A human approval step should bind a reviewer’s decision to the exact proposed action. Pausing a workflow is insufficient if the payload can change, the reviewer lacks authority, or execution resumes after the proposal becomes stale.
Approval is a business control
Human approval evaluates a defined action before its side effect occurs. The reviewer needs the resource, proposed changes, relevant evidence, consequences, and a clear approve-or-deny choice.
n8n documents human review for AI tools, where a workflow waits for a person’s decision before a selected tool runs. Treat that platform capability as part of a wider permission and freshness design.
For a proposed demonstration, store a proposal revision and intended operation reference. Authenticate the reviewer through the supported channel and enforce the business role at the execution boundary. A forwarded approval message should not silently grant another person authority.
Review a fictional customer-record deletion
The AI proposes deleting one duplicate customer record. The approval view shows which record, why it appears duplicate, what linked data is affected, and what remains uncertain. The reviewer denies because a later service request is attached.
A second fixture changes the proposal after approval. The original decision must not authorise the new record or broader scope. If the target changes independently before execution, apply the defined conflict rule and require a fresh review where necessary.
| Approval fixture | Expected result |
|---|---|
| Authorised reviewer approves current proposal | Continue to final backend checks |
| Reviewer denies | No proposed side effect |
| Unauthorised person responds | Decision rejected |
| Proposal changes after approval | Earlier approval invalidated |
| Request expires | No indefinite later execution |
Inspect actual records and operation history. An approval notification being delivered is not proof that a qualified person reviewed the action or that the executed payload matched it.
Design for absence and denial
Give approvals an owner, expiry, and escalation policy. Silence should not automatically mean permission unless a specific authorised workflow defines such a rule. The caller or staff interface must accurately show pending approval rather than completed work.
Human review adds latency and staffing requirements. Use it where the consequence warrants oversight and keep the view concise enough for meaningful review. A high-volume queue of vague requests can become mechanical clicking rather than an effective control.
This approval demonstration is proposed. The voice integration case study provides related workflow context. Pair it with external approval queue design.
n8n approval FAQ
Does approval replace tool permissions?
No. The execution service still enforces identity, resource scope, and current business rules.
Can approval survive a changed payload?
Only under an explicit rule preserving its meaning. Consequential changes normally require a new decision.
What should happen when nobody responds?
Follow the defined expiry or escalation path and keep the operation pending or closed accurately.