Flow Control

Components that shape how a workflow advances rather than performing on-chain or external work. All four are free (billing: 0) and execute purely in-process.

---

BRANCH

BRANCH Workflow

Conditional routing. Takes a boolean and forwards execution down either the true or false sequence edge.

Inputs

Sequence outputs

• true — followed when condition is true
• false — followed when condition is false

Use BRANCH alongside conditions emitted by your data components (e.g. IS_EVM_GNOSIS_SAFE_DEPLOYED.deployed) to short-circuit work that isn't needed.

---

RETURN

RETURN Workflow

Emits a value from the workflow that is tracked through get_workflow_run / the run-status API. Use this to declare what an automation produces.

Inputs

Dynamic — every connected input becomes a field on the returned object.

Behaviour

The returned object is attached to the workflow run record and retrievable via:

• GET /v1/sdk/workflow-executions/{runId} (REST)
• get_workflow_run (MCP)
• runs.subscribe(runId) event stream (SDK)

A workflow can have multiple RETURN components; results are keyed by the component ID.

---

SEQUENCER

SEQUENCER Workflow

Fan-out helper. One inbound sequence edge → an unbounded set of named outbound edges that all fire when the sequencer runs. Use it to start independent parallel branches from a single trigger.

Sequence outputs

Add as many named output edges as you need on the canvas. Each edge fires in parallel when the sequencer is reached.

---

FORWARDER

FORWARDER Workflow

Pass-through that forwards a value across the canvas without modification. Useful for routing one upstream output into many downstream consumers via a shared "anchor" node, or for keeping the visual graph tidy when wires would otherwise overlap.

Inputs

Outputs