Human-in-the-loop
Pause a workflow for a human to approve or reject before it continues.
Automation should not remove people from decisions that need judgment. The Human Review action puts a person in the loop: it pauses a run and waits for someone to approve or reject the records before the workflow continues.
Add a review step
- Open your workflow in the editor (Ecosystem › Workflows, then the workflow).
- In the Configure tab, find Human Review in the Collaboration group, or type it into Search actions..., and place it where the pause should happen.
- Optionally fill in Issue Summary, the message the reviewer sees, for example Review AI-drafted email before sending. Leave it empty and SPARK writes a summary from the record count.
- Click Save, then activate the workflow so it can run.
Human Review is a planned gate: every run that reaches it pauses, and every record the step receives goes to the reviewer. When the records are resolved, the step passes the approved records on. See Build a workflow for the full build-and-activate flow.
Find work waiting for review
Paused runs surface in two places:
- In the Executions tab, the run shows the Awaiting review status.
- In the Interventions tab, each pending review appears as a row with columns for Task, Status and Created. Use the status filter (All, Pending, Resolved) and the search box to focus on what still needs a decision.
Other steps use the same tab: Resolve Relations sends unknown reference keys here too.
Approve or reject
- In the Interventions tab, click a row, or choose Open intervention from its ⋯, to open the review on its own page. Review in the same menu opens it in a dialog instead, and Copy link copies a link to it.
- The page shows the summary and counts, then the records in a grid with columns such as Record Data, Status, Resolved By and Created. Filter by status (All statuses, Pending, Approved, Rejected) to focus.
- To correct data before deciding, use a record's Edit record control; an edited record is marked Edited.
- Select the records to decide on with their checkboxes (or Select all).
- Choose a decision from Select action..., such as Approve or Reject.
- Click Apply. The Resolved By column then records who resolved each record.
A record moves from Pending to Approved or Rejected once you apply a decision. Only after the flagged records are resolved does the paused run leave Awaiting review and continue.
Reviews that create data, not just decisions
Human Review asks a yes or no question. Resolve Relations uses the same Interventions tab for a different kind of question: incoming rows reference something your reference data does not hold, and the reviewer decides what that something is.
The differences worth knowing:
- One item per distinct unknown key, not one per row, so hundreds of rows referencing two unknown sub-funds are two questions.
- The decisions are Approve (link to an existing record), Create new records, Approve without linking, and Reject.
- Creating records is a bulk step: one row per key, pre-filled from the incoming data, all created together.
See Resolve relations.
Statuses you will see
Review tasks and their records carry a Status: Pending while they wait, In progress or Submitted while a decision is being applied, Approved or Rejected after a decision, and Resolved once the task is complete.
Where to go next
- Follow a run through its pause in Executions.
- Reconcile against reference data in Resolve relations.
- Revisit the building blocks in Build a workflow.
- For work that needs reasoning rather than a yes or no gate, hand steps to an agent with Ask an agent.