Approvals
Pause a workflow until an authorized person approves or rejects.
Workflows is in Beta. The UI and API may change. The sidebar entry is currently disabled for most workspaces — your account team enables it for pilot orgs.
The Approval node pauses a run until an approver decides yes or no. Use it to keep a human in the loop before destructive or high-cost steps.
Configuring an Approval node
In the Properties drawer, set:
- Approver criteria — any admin, a specific user, or a team.
- Timeout — a duration such as
24h. When the timeout elapses, the run follows the timeout edge. - Prompt — the message the approver sees. Include enough context — node ids, upstream values — so they can decide without opening the full run detail.
The timeout edge defaults to the rejection path if no explicit timeout edge is drawn.
What the approver sees
When a run reaches an Approval node, a new item appears in the global Approvals view. The approver sees the prompt, the run id, a snapshot of relevant upstream outputs, and Approve / Reject buttons. Each decision is recorded with the actor's identity and a timestamp.
Resuming the run
The run resumes along the matching edge:
- Approve — follows the approve edge.
- Reject — follows the reject edge.
- Timeout — handled by
approvalTimeout, follows the timeout edge.
Downstream nodes receive the decision (approved / rejected / timed out) and the actor as part of the Approval node's output.
Permissions
Only users matching the approver criteria can act on a pending approval. Members outside the approver scope see the approval as read-only in the Approvals view.