Approval gate
Pauses the workflow until a human approves (or rejects) via an email link or the admin queue.
Why use it
Some side effects shouldn't run automatically — bulk email sends, customer refunds, content publishing. The approval gate stops the workflow, queues the pending decision, notifies an approver, and resumes when they click Approve.
Inputs
| Field | Type | Description |
|---|---|---|
payload | any | Data to show in the approval UI |
summary | string | One-line description of what is being approved |
Configuration
- Approver email (required): who gets the notification. Can be a token, e.g.
{{trigger.workflow_owner.email}}. - Auto-approve after: optional timeout (e.g. 24h). If no human approves within the window, the workflow either auto-approves OR takes the rejected branch — your choice.
- Cancel after: optional max wait (e.g. 7 days). Workflow ends with
cancelledstatus if neither approval nor rejection comes.
Outputs
- approved — fires when an approver clicked Approve. Payload includes
approver_user_id,approved_at,approval_note. - rejected — fires when an approver clicked Reject. Payload includes
rejection_reason.
What the approver sees
An email with the approval summary, the trigger payload formatted as a table, and two big buttons: Approve and Reject. Clicking either opens a confirmation page on the WP admin where they can add a note before confirming. The link contains a single-use, signed token; expires after 7 days.
The admin Setyenv → Pending approvals queue lists every waiting approval with the workflow name, age, summary, and the same approve/reject actions.