The Approval node pauses workflow execution until someone approves or rejects the step. Use it for human-in-the-loop workflows — expense sign-off, content review, deployment gates, etc.
Configuration
| Field | Description |
|---|---|
| Message | What the approver sees (supports {{templates}}) |
| Approver email | Who receives the approval request |
How it works
- Upstream nodes run normally until the Approval node.
- Execution pauses and sends a request to the approver.
- When they approve, execution continues to the connected downstream nodes.
- When they reject, the workflow follows the rejection path (if configured) or fails.
Example message
Please approve sending this campaign to {{lastOutput.recipientCount}} contacts.
Campaign: {{variables.campaignName}}
Requested by: {{inputs.requestedBy}}
Tips
- Place Approval after any transforms that prepare the data the approver needs to review.
- Use workflow variables for campaign or environment names so the same workflow works across stages.
- Combine with Condition nodes after approval for approve vs reject branches.
- Test with a Manual trigger and your own email as approver before going live.