Workflows
A process assembled on a canvas: steps, conditions, external calls, and waits. Versions, runs, and how a workflow differs from an autopilot.
A workflow is a process built from steps on a visual canvas: hand work to an agent, check a condition, call an external service, send an email, wait for an event. You reach for one when a single issue is not enough and the order and the branches have to be fixed in advance and repeat identically.
Workflows live in the Automations section next to autopilots and Assetflows.
Draft, version, run
- A draft is what you edit. Drafts never execute.
- Publishing freezes the current draft into a version and makes the workflow runnable. Every publish creates a new version; earlier ones stay unchanged.
- A run is one execution of a published version, with its own input and its own history.
Editing the draft does not touch the running version: until you publish again, runs keep using the old one. A workflow can also be disabled — no new runs are created, while those already going finish.
The designer
Steps are dragged from the node panel onto the canvas and connected top to bottom, from Start to Stop. Selecting a step opens its settings on the side.
Values travel between steps as substitutions: a step can read what the run started with, or the result of an earlier step. In a field it looks like this:
{{start.payload.order_id}} the run's input
{{steps.fetch.body}} the response of the step whose id is fetchA workflow is validated before publishing: if any step has errors, it cannot be published, and the offending steps are highlighted.
What a process is built from
| Category | Node | What it does |
|---|---|---|
| Agents | Agent task | Dispatches an agent or a team leader with a title and instructions |
| Flow | Decision | Sends the run down a branch. "By rule": the first rule that matches, else the default branch; yes/no is one rule. "By meaning": asks the workspace's model and follows its answer — yes or no, one of the options, or a score on a scale whose number later steps get. Below a confidence threshold it can go down a "Not sure" branch; the question, the probabilities and the model show in the run's thread |
| Wait | A pause of a set length — from a second to 30 days | |
| Wait for autopilot | Suspends the run until a chosen autopilot fires | |
| Group | Folds a sequence of steps into one collapsible block | |
| Integrations | HTTP request | Calls an external service and passes the response to later steps |
| Messaging | Send email | Sends mail over SMTP using workspace credentials |
The agent task step is fire-and-forget: it reports whether the task was queued or skipped, and a skip is a normal outcome you can branch on rather than a failure.
What starts a run
- By hand — the button on a published workflow, optionally with input.
- By an autopilot — on a schedule, or on a webhook from an external system.
- By an agent — an agent can start any published, enabled workflow.
A workflow has no webhook address of its own. When a process must start from an external event, the webhook goes on an autopilot and the autopilot starts the workflow. Autopilots are the single inbound-event surface; workflows are the single durable-orchestration surface.
Waiting for events
The Wait for autopilot node turns a workflow into a long-lived process: the run sleeps and wakes when the chosen autopilot fires, and the data that arrived with the event becomes available to the steps that follow.
A wait can be tied to a correlation key, so parallel runs each wait for their own event: the run
for order 1234 wakes on that order's event and no other. There is no timeout — a suspended run waits
for its event, or for you to cancel it.
Runs
Every execution is recorded: who started it, which version it ran, how long it took, and which step it is on. The statuses are Running, Waiting, Completed, Failed, Cancelled.
The runs view shows period totals (how many ran, completed, failed, and are active now), each step's duration, and the error text when a step breaks. Because run state is stored durably, a waiting process is a real execution you can watch and cancel.
Building and moving one
- Generate with an agent — describe the process in words and let an agent assemble the draft, then edit it by hand.
- Duplicate — start from a workflow that already works.
- Import and export — a workflow can be exported to a file and loaded into another workspace.
Workflow or autopilot
- An autopilot is the "when": a schedule, a webhook, a button. It can file a task or start a workflow, but it cannot branch.
- A workflow is the "what": a sequence of steps with conditions, external calls, and waits. It does not start itself.
A full process usually uses both: the autopilot catches the event, the workflow works it.
Next
- Credentials — the secrets nodes use to reach external systems.
- Autopilots — what starts a workflow.
- Assets — an Assetflow on a table can start a workflow too.