Wait node¶
Status: Current | Last reviewed: 2026-07-07
Suspends the workflow until a duration elapses or an event arrives.
Behavior¶
Supports multiple parallel conditions - the first to fire resumes. For event waits, send a workflows-api event with the configured event_type; include payload.workflow_execution_id or payload.execution_id to target one running workflow execution. On resume, the event payload is stored at node_results[<node_id>] and flattened for merge templates such as {{<node_id>.ticket_id}}, with the full body also available as {{<node_id>.payload.ticket_id}}.
You can add this node from the workflow editor add-node menu when building a flow.
This node can suspend a workflow run and resume later. Avoid it in workflows that must return synchronously to the caller.
- Wait nodes suspend the run. They are not allowed in synchronous workflow execution mode.
- Duration waits resume automatically. Event waits resume when workflows-api receives a matching event for the same workflow execution.
Configuration options¶
| Option | Required | Type | Values / default | What it controls |
|---|---|---|---|---|
Wait conditions (wait_conditions) |
No | array | First condition to fire resumes the workflow. |
Outputs¶
| Output | Type | What it contains |
|---|---|---|
status |
string | 'waiting' or 'resumed' |