Human Intervention
Pause a run for a person to review and approve, then resume automatically.
Some workflows need a human in the loop — an approval, a manual data entry, a sign-off before anything irreversible happens. The Human Intervention action pauses a run at a chosen point, hands a person a form to complete, and resumes once they submit. It turns an otherwise fully automated rule set into one that can wait on a decision.
The flow at a glance
- A run reaches a Human Intervention action and stops, recording a pending intervention.
- A secure, time-limited public link is generated for a reviewer.
- The reviewer opens the link, fills out the form, and submits.
- The submission is checked, and the configured continuation rule set is queued to resume.
Configuring the action
When you add a Human Intervention action you configure how the pause behaves:
- Continuation rule set — the rule set that runs to resume the workflow once the reviewer submits.
- Form — the fields the reviewer sees, authored as a runtime form. Existing context values can be passed through so the reviewer has what they need to decide.
- Link expiration — how many hours the link stays valid (default one hour). It cannot be set longer than the run remains available to resume.
- Maximum uses — how many times the link may be submitted (default one).
- Generated link context key — the context key that receives the generated link, so an earlier action (for example an email) can deliver it to the reviewer.
The public intervention page
The reviewer does not need an account. The generated link opens a standalone public page that loads the form. The reviewer completes the form and submits; on success the page shows the correlation id of the resumed run.
A link is rejected, and the reviewer is told why, when:
| Condition | What the reviewer sees |
|---|---|
| The link is invalid | Not found |
| The link has expired | Link has expired |
| The maximum number of uses is reached | Already used the maximum number of times |
| The original run is no longer available | Link has expired |
Resuming the run
When a valid submission is accepted, the reviewer's form input becomes context and the configured continuation rule set is queued in the same environment. From there it proceeds like any other run, and the whole sequence stays stitched together under one correlation id in the logs. On a Shared or Free tier environment, the resumed run counts against your monthly run allowance like any other.