n8n approvals

n8n form approvals with email decisions and callbacks

Collect approval decisions before n8n fulfillment runs, with FormNode approval fields, decision tables, email actions, and callback payloads.

Build an approval formRead approval docs
Direct answer

n8n form approvals are workflows where a submitted request needs a human decision before n8n performs the work. FormNode handles the approval surface with email actions and decision tables, then sends the approval result back to n8n with the original form context.

Email decisionsApprovers can approve or reject from email without touching n8n.
Decision tablesRows can carry individual approve/reject decisions and scheduling data.
Callback-readyApproval outcomes can call n8n with the request, decision, actor, and context.
Use this when

The form is part of the workflow, not just the front door.

  • A provisioning, access, firmware, purchasing, or change request needs signoff before n8n runs.
  • Approvers should not need to log into n8n or a PSA to make a simple decision.
  • The workflow needs a structured approval result, not a ticket comment or forwarded email.
  • Some requests need per-row decisions, scheduling choices, or rejection reasons.
Workflow pattern
Collect the requestUse FormNode to collect the intake data and source-system IDs needed by n8n.
Route the approvalSend the approval to the right manager, customer contact, or operations owner.
Capture the decisionStore approve, reject, comments, decision-table rows, and approver metadata.
Call n8nSend the result to n8n so the workflow can fulfill, cancel, update a ticket, or ask for more data.
Concrete workflow example

Firmware upgrade approval

n8n detects available firewall updates, creates a FormNode decision-table approval, and waits for the customer to approve or reject each device.

The approval callback tells n8n exactly which devices were approved, which were rejected, and what schedule should be used for the approved work.

What the page proves
FieldsDevice, Current version, Target version, Maintenance window, Approve or reject
Systemsn8n, NinjaOne, SonicWall, ConnectWise, FormNode
Comparison

Why a workflow-first form layer matters

CriteriaGeneric formsFormNode
n8n-only approvalBuilt from email, wait, and workflow nodesManaged approval surface with decision capture and callback payloads
Ticket comment approvalEasy to miss and hard to parse reliablyStructured approval state and approver metadata
Jotform/Typeform + n8nCan collect a decision, but approvals are not the operating modelApproval fields and decision tables are native workflow primitives
Customer experienceApprover jumps between toolsEmail and portal approval surfaces; Business adds full branding controls
AuditabilityScattered across workflow history and messagesApproval record tied to the form submission and organization
Common questions

Can n8n wait for a FormNode approval?

Yes. n8n can create or receive a FormNode approval workflow and continue when FormNode sends the approval result back through a callback or webhook.

When should approvals live in FormNode instead of n8n?

Keep simple internal waits in n8n. Use FormNode when the approval is customer-facing, needs email or portal UX, needs decision tables, or needs an auditable approval record tied to a form submission.

Related FormNode pages