Human in the Loop
Pause a workflow for a person to review, then approve and resume or reject
The Human in the Loop block pauses a running workflow and waits for a person to make a decision. The reviewer sees the workflow's output so far, then either approves (the workflow resumes) or rejects (the workflow stops). Use it for sign-offs, approvals, and any step where a human must decide before automation continues.
A paused workflow waits indefinitely until a reviewer acts — there is no automatic timeout. Reviewers are notified and can open the review from their notifications.
When to use it
- Approvals — a refund, a contract, a publish step that needs sign-off.
- Quality gates — a person checks an AI-generated draft before it goes out.
- Compliance — a required human decision is recorded before the process continues.
What the author configures
| Setting | What it does |
|---|---|
| Review Question | The question shown at the top of the review panel. Supports variables like <blockName.field>, resolved to the workflow's real values when it pauses. |
| Paused Output (Context) | The fields the reviewer sees — the workflow output they need to decide. Reference upstream blocks with <blockName.field>. |
| Resume Form Fields | Optional typed inputs the reviewer fills in (text, number, boolean, …). Each becomes available to downstream blocks after resume. |
| Approver Notifications | Optional notifications (e.g. Slack, email) sent when the workflow pauses. |
| Reviewer Role | Who may resolve the pause — owner, admin, or member. |
| Resolution | First claim (any one reviewer decides), All must approve, or Quorum (N reviewers). |
What the reviewer sees
When a reviewer opens a paused workflow, the review panel shows, in order:
Status — Paused, Queued, Resuming, Resumed, or Rejected.
AI advisory (when an LLM integration is configured) — a short, grounded decision brief that summarizes what to weigh, drawn from the workflow's paused output. Expand Reasoning details to see how the AI weighed the information.
The advisory is decision support only — it never states "approve" or "reject", and it never decides for you. You make the decision. It is grounded in the paused output the workflow surfaced; if there is nothing to ground on, no advisory is shown.
Review question and paused output — the author's question (or a one-line summary) and the context table of workflow values to review.
Resume form — any inputs the author asked the reviewer to fill in.
Approve or Reject — Resume Execution continues the workflow; Reject stops it.
Approve vs. reject
- Approve / Resume — the workflow continues from where it paused. Any resume-form values are passed to downstream blocks.
- Reject — the workflow stops and cannot be continued. A rejected pause is terminal: the status becomes
Rejectedand the workflow will not resume. You can add an optional reason, which is recorded with the decision.
Rejection is final. Once a pause is rejected, that workflow run is over — re-opening the review will not let you resume it. If a workflow should be able to continue down a different path instead of stopping, model that with a resume-form field (e.g. a boolean the reviewer sets) and a Condition block, rather than Reject.
Opening a review
Reviewers receive a notification when a workflow pauses. Opening the notification takes you straight to the workflow with the review panel open, where you can read the context and decide.
Multiple reviewers
With All must approve or Quorum, the workflow stays paused until enough reviewers have submitted. The AI advisory is generated once per pause and shared across all reviewers — everyone sees the same brief.