Place a human decision before an action whose impact, uncertainty or difficulty of reversal exceeds your team's agreed tolerance. The boundary should protect a specific business consequence, not merely add an “approve” label somewhere in the process.
Identify the last safe pause
Find the point before money, external communication, access or another consequential state changes. Ask what preparation can safely happen earlier and what must wait for a decision.
n8n documentation establishes workflows as connected nodes. The supplied evidence does not establish built-in approval nodes or particular pause mechanisms. Treat the approval boundary as a process requirement, then verify how an eventual implementation could satisfy it.
Approval after an irreversible action may provide acknowledgement, but it cannot serve as permission for that already-completed action.
Use an impact-and-reversibility worksheet
Complete a card for each proposed side effect:
- Impact: who or what could be affected, and by how much?
- Reversibility: can the action be corrected, and what remains after correction?
- Uncertainty: which facts or judgements are unresolved?
- Reviewer: who has authority and sufficient context?
- Decision packet: which minimum fields support an informed choice?
- Expiry: which changes invalidate the decision?
- No response: should work remain held, expire or escalate?
For privacy and rights, ask whether reviewers need every field and whether they are authorised to see it. These are review questions, not legal conclusions.
Compare two hypothetical actions
A fictional Kochi design studio considers two synthetic cases. Case A recalculates an internal estimate from 6 hours at ₹800 per hour to ₹4,800. Case B sends a final ₹48,000 commitment to an external supplier.
Under an illustrative team policy, the internal calculation may proceed without approval because it creates no external commitment. The supplier instruction requires a named reviewer to confirm amount, scope and supplier reference before release.
Test three variations: the amount changes to ₹52,000 after approval; the reviewer does not respond; the supplier reference changes. The proposed contract should invalidate stale approval for changed material facts and keep unanswered work held or escalated, not silently approved.
These thresholds and outcomes are hypothetical business choices, not recommended universal limits.
Stop approval without context
Stop if the reviewer cannot see the exact proposed action or if nobody owns unanswered requests. Next, agree the decision packet, expiry conditions and escalation route before selecting implementation details.
For access planning, check the automation catalog for access format and saved terms before buying. Marketplace account/code/token offers are not proof of official subscription equivalence or approval capabilities.
Sources and scope
Source material checked 29 October 2026; features/policies may change. n8n workflow documentation supports the connected workflow model. The worksheet, thresholds and approval contract are editorial process advice, not documented approval features.