An approval queue outside the automation platform can give staff one consistent review surface. It needs its own permissions, proposal versions, expiry rules, and execution contract to avoid becoming an unsafe generic resume button.
External approval separates review from orchestration
An external approval queue stores proposed business actions independently of the workflow runner. The automation submits a proposal reference and waits or polls according to the supported design. Approval authorises only the identified current proposal.
For a proposed record, include action type, target resource, validated arguments, evidence links, revision, requesting operation, reviewer scope, expiry, and decision state. Keep secret values and unnecessary personal content outside the broad review view.
The execution service should claim an approved proposal atomically and recheck any time-sensitive prerequisites. A staff approval does not freeze appointment availability or prevent another employee from changing the target record.
Test a fictional refund proposal
A workflow asks a manager to review a refund request. The queue shows the relevant transaction, requested amount, evidence, and uncertainty. The manager approves one proposal revision. A later edit increases the amount; that change must invalidate the earlier decision.
Now simulate two workers receiving the approval event. Only one may initiate the approved effect under its duplicate-protection contract. The queue state and the external result must remain linked for audit and recovery.
| Approval case | Required invariant |
|---|---|
| Authorised current approval | Only the bound proposal may execute |
| Denial | No proposed effect |
| Proposal changed | Fresh decision required under policy |
| Expired request | No unexpected later execution |
| Worker response lost | Reconcile the effect before repetition |
Use controlled fictional records and a fake execution service. Test the permissions on the queue API directly rather than relying on hidden buttons in its interface.
Decide which system owns completion
The queue can own the decision while the execution service owns the effect. Represent approved, executing, completed, failed, and uncertain distinctly. A reviewer clicking approve is not proof that the action completed.
An external queue adds infrastructure, authentication, and operational support. Its benefit is a stable staff workflow across several automation tools. Choose it when that consistency and stronger domain control justify the additional boundary.
This approval architecture is proposed. The HVAC case study describes a staff-facing operations product without claiming an external approval service. See human review in n8n for a platform-specific alternative.
External approval FAQ
Should a workflow trust any callback claiming approval?
No. Verify the sender, reviewer authority, proposal identity, and current decision state.
Can approved work remain executable forever?
Use a defined expiry and freshness policy rather than indefinite permission.
What should staff see after approval?
Show execution progress and authoritative completion or uncertainty separately from the decision itself.