Customer approval forms for n8n
Use FormNode customer approval forms to pause n8n workflows until a customer approves, rejects, comments, or decides per row.
A workflow should not provision access, schedule maintenance, buy licenses, or change infrastructure before the right person approves. Approval state needs to be structured, auditable, and easy for n8n to branch on.
The n8n approval pattern
FormNode captures the human decision. n8n waits for the callback and only runs the approved path.
Create the approval surface
Build an approval form with approve/reject fields, comments, context data, or a decision table for per-row outcomes.
Send the approval to the right person
Create the approval from the API, MCP, or a FormNode action and route it to the approver by email or portal.
Receive the n8n callback
Point the approval callback at an n8n webhook and branch on the decision, status, comments, response data, and approval ID.
Make every branch explicit
Handle approved, rejected, expired, and missing-callback cases separately so n8n does not treat silence as approval.
What FormNode owns in this n8n workflow
Email approval links without requiring a portal login
Decision tables for per-row approval outcomes
Structured approval.responded callback payload
Retry handling for callback delivery
Approval ID for idempotent n8n continuation
Comparison
| Approach | Best fit | Tradeoff |
|---|---|---|
| Manual ticket comment | Informal approvals | Hard for n8n to parse reliably and audit later |
| n8n wait node only | Internal technical approvals | No managed customer-facing approval surface |
| FormNode + n8n | Customer approvals that need a structured callback | Approval UX lives in FormNode; workflow continuation lives in n8n |
Related implementation docs
Build the form layer. Keep n8n as the engine.
Start with one workflow-heavy form. Add live fields, approvals, portal context, and tracked delivery when the form becomes operational.
Get Started Free