Wait For Approval
Wait For Approval
Section titled “Wait For Approval”Pause a run and wait for a human decision before continuing.
What it does
Section titled “What it does”Pauses the run until a person approves or rejects it. The node produces no output on its own — the run parks and waits for a decision. When a decision arrives, the items that were waiting flow out of the port the decision chose: Approved or Rejected. Use this as a checkpoint before any consequential action that warrants a human sign-off.
When to use it
Section titled “When to use it”- Any human-in-the-loop checkpoint before a consequential step: sending an email, making a purchase, publishing content, or triggering an external action.
- The work after Approved runs only on approval; Rejected is an ordinary branch for handling a no or fallback behavior.
- When waiting indefinitely is acceptable — the run survives browser restarts and remains in the Executions pane until approved, rejected, or manually cancelled.
Inputs and settings
Section titled “Inputs and settings”| Setting | Notes |
|---|---|
| Prompt | The question or text shown to the person making the decision. Appears on the paused run in the Executions pane. |
Outputs
Section titled “Outputs”The node draws two output handles:
- Approved — Items flow here when the person approves the run.
- Rejected — Items flow here when the person rejects the run.
Paused run visibility and control
Section titled “Paused run visibility and control”A paused run appears in the Executions pane, where a person with access can approve, reject, or cancel it. The run waits indefinitely — it does not time out or resume on its own — and persists even if the browser restarts or the window closes. Cancelling a paused run stops it without flowing items to either output.
Wait For Approval vs. action approval
Section titled “Wait For Approval vs. action approval”This node is a durable checkpoint you design into a flow: it pauses a whole step, waits indefinitely, and survives browser restarts. It is different from the live action approval that gates the model-driven action tools (Browser Tool, HTTP Request Tool, MCP Client Tool) — that gate is automatic, fires on each action the model decides to take, and auto-rejects after a timeout. Use this node for deliberate human sign-off on a step; the action gate is always-on and requires no node. See Action Approval.