n8n approval form template
A human approval form structure for n8n workflows that need approve/reject decisions, comments, decision tables, and callback payloads.
An n8n approval form template should capture the original request, approver identity, approve or reject decision, rejection reason, optional scheduling data, and callback context so n8n can continue, cancel, or reroute the workflow.
Use this template when the form is part of an operational workflow.
- Access requests, purchasing requests, firmware approvals, and change approvals.
- Customer-facing approvals where the approver should not log into n8n.
- Workflows that need structured decisions instead of ticket comments.
Typical systems this template may need to read before n8n fulfills the request:
Fields this form should include
Keep the approval action simple for the approver, but preserve enough metadata for n8n to branch cleanly after the decision.
Use an approval callback webhook or n8n resume endpoint that receives the decision, approver, original submission ID, and selected decision-table rows.
Build the form first, then wire the workflow.
Create the request view
Show the request details n8n needs the human to approve.
Capture structured decisions
Use approval fields and decision tables instead of free-form replies.
Send the callback
Return the decision payload to n8n with submission and approval IDs.
Branch in n8n
Continue approved work, cancel rejected work, or update a ticket with the result.