Business modulesWorkflows

Workflows and automations

Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.

Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.

Where to find it

Web: open Workflows. Desktop: Business → Workflows, using the same record paths. Disabled modules or missing read permission remove the navigation entry.

Screen / tabWeb pathUsageDesktop
Workflows/workflowsList, view or tabNative screen
Automations/automationsLegacy redirect → /workflowsNative screen
Record details/workflows/[workspaceId]Record or editorNative screen
Record details/workflows/[workspaceId]/[workflowId]Record or editorNative screen
Blocks/workflows/runs/[runId]Record or editorNative screen
Record details/workflows/rules/[id]Record or editorNative screen
Runs/automations/runsList, view or tabNative screen
Record details/automations/[id]Record or editorNative screen
Record details/automations/runs/[runId]Record or editorNative screen

Start working

Step 1

Choose a draft/template.

Step 2

Add triggers/blocks and inputs.

Step 3

Map module events into actions.

Step 4

Test/review/deploy.

Step 5

Inspect runs/waits; stop listening or decide/cancel.

Workflows and automations
Workflows and automations — Desktop
Workflows and automations

Settings

Option-by-option configuration and screen paths: Settings guide.

There is no separate settings route; the guide distinguishes record options from declared defaults.

Permissions and limits

Before you start

Drafts do not deploy. Actions use the deployer’s current permissions. Legacy automation links redirect to canvas workflows.

Role capabilities: Read (read), Write (write), Delete/archive (delete), Manage (manage), Export (export).

Own-record restrictions apply equally to lists, records and Era. Record state or missing data can refuse an otherwise permitted action.

Ask Era

Draft a workflow notifying an owner on a new application.

Select relevant records for Era context. Era respects modules/roles; external or confirmation-sensitive work can stop for approval. Use era tools in the terminal to inspect currently available tools.

Automation and events

These declared events are available to module-event triggers. Subscribing does not configure the next operation; choose recipients, conditions and actions separately.

Operation details

The inventory includes record, configuration, visitor and background flows. IDs support Era/automation; not every row is a menu button. Asterisks mark required inputs. Unmapped rows do not imply a visible control.

Operation and IDInputsPermissionScreen or flow
Draft a workflow · workflows.draftName *, When this happens, Trigger, Trigger settings, Description, Only when, StepsManageRecord/API/visitor flow; no separate screen button mapped
Start a workflow from a template · workflows.install_templateTemplate *, AnswersManageRecord/API/visitor flow; no separate screen button mapped
Start a workflow on a module event · workflows.subscribe_canvasCanvas workflow *, When this happens *, Listening, Stop a waiting run whenManage/workflows
Stop a workflow listening to events · workflows.unsubscribe_canvasCanvas workflow *ManageRecord/API/visitor flow; no separate screen button mapped
Park a workflow run at a wait · workflows.park_canvasCanvas workflow *, Canvas execution *, Pause point *, Waits for *, Until, Approval task, Block, Trigger eventWriteBackground routine
Approve or reject a waiting workflow · workflows.decide_waitWaiting run *, Approve *, NoteWrite/workflows/runs/[runId]
Cancel a waiting workflow run · workflows.cancel_waitWaiting run *Write/workflows/runs/[runId]
Remember a step’s idempotency key · workflows.record_step_keyCanvas workflow *, Block *, Key *, Canvas execution, ResultWriteBackground routine
Report a failed workflow run · workflows.report_run_failedCanvas workflow *, Canvas execution *, Workflow, ErrorReadBackground routine
Record an undo of a workflow run · workflows.note_undoCanvas workflow *, Canvas execution *, Outcome *, Steps *WriteRecord/API/visitor flow; no separate screen button mapped

Technical sources

packages/os-kernel/src/modules/workflows.ts, packages/os-kernel/src/modules/index.ts, apps/studio/lib/os/navigation.ts, apps/studio/lib/os/settings-groups.ts, apps/era-station/apps/web/src/era/business/screens.ts.

Desktop editor surfaces: apps/era-station/apps/web/src/era/surfaces/workflow/WorkflowCanvasScreen.tsx.

Screen pictures