Logic & flow nodes

Triggers and actions cover what happens; logic and flow nodes control how the workflow moves — splitting a path in two, pausing, ending a branch, or reaching out to another service.

Decision nodes

A Decision node branches the workflow: it evaluates one or more conditions, then follows the True path when they're met and the False path when they aren't.

Set one up

1. Add a Decision node to the canvas.
2. Add one or more conditions.
3. Choose whether all conditions must be true (AND) or any condition can be true (OR).
4. Connect the True and False handles to different next steps.

Condition fields and operators

Each field offers only the operators that make sense for it:

The Variable field reads any value produced earlier in the run by dotted path — an AI-extracted field (ai_extraction.extractedData.sentiment), a webhook payload value (trigger.payload.total), or any step output. Its is greater than / is less than operators compare numerically, so you can branch on amounts, counts, or scores.

Delay nodes

A Delay node pauses the workflow for a set time before the next step runs — the backbone of follow-ups and reminders.

Set the delay

Pick a duration and a unit:

• Minutes — quick follow-ups
• Hours — same-day automation
• Days — longer sequences

Or tap a preset: 5m · 15m · 30m · 1h · 2h · 24h · 1d · 3d.

End nodes

An End node stops a branch. Nothing else runs once the workflow reaches it — but other branches keep running independently.

Every workflow needs at least one, and every step has to lead to one. Publishing checks both: a graph with no End node, or with a step that reaches none, is refused and the error names the steps left hanging. So a Decision where only one side should carry on still wires the other side to an End node.

Drafts are exempt — the editor autosaves a half-built canvas without complaining, and only publishing runs the check. You rarely add an End node by hand either: the editor puts one on the canvas with your first step and keeps one there. Add more when separate paths should finish in visibly different places.

Simple API Request nodes

The Simple API Request node calls an external service directly — no code. It isn't in the left sidebar; add it from the command bar with ⌘K.

Configure the request

• HTTP Method — GET, POST, PUT, PATCH, or DELETE
• Request URL — must start with http:// or https://. Supports {{...}} templating.
• Headers — custom headers like Authorization or Content-Type
• Request Body — for POST, PUT, and PATCH, the payload to send (templating supported)

The response is stored on the step, so downstream nodes can read {{<step>.response.body}}, {{<step>.response.status}}, and header values — pull a value out of the response with a Decision node's Variable condition, or drop it into a later message.

What it's for

• Forward conversation or webhook data to your own endpoint
• Look up a customer in an external CRM and branch on the result
• Trigger an action in another tool on a specific event
• Post to an alerting or logging service (pairs naturally with the Workflow Error trigger)

Related