Automation
Approval Gate
Stops the run and asks a person to approve before it carries on — for example before a step that writes to production. Approved, the steps after the gate run with the rows it held; rejected, the run ends there.
When to use it
Use it in front of irreversible steps, when a human should look at the numbers first.
In a pipeline
File InputApproval GateSQL Server Output
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Approver (email or user name) | text | Yes | lead@example.com |
| Message to the approver | textarea | — | Check the totals before they are loaded. |
| Wait up to (hours) | number | — | 24 |
| If nobody answers | select | — | reject |
Example
Approve before loading production
- Approver (email or user name)=lead@example.com
- Wait up to (hours)=24
- If nobody answers=End the run there
The approver sees the rows on the Approvals page (Tools ▸ Approvals) and, when email is set up, gets a message.
Worth knowing
- The flow must be saved: an approved run carries on from the flow as saved, without repeating the steps before the gate.
- The approver must be a FlowDoo user, named by email or user name. They cannot see anything but the rows the gate holds.
- A gate holds at most 50,000 rows — summarise before it for big loads.
- Previews pass straight through the gate. Approval Gates do not work inside sub-flows.