This is the setting that decides whether your automation saves you time or puts you at risk. Placed well, it costs a few seconds a day. Placed everywhere, it cancels the gain. Missing where it was needed, it ends up writing to your customers on your behalf.
Definition
Human in the loop refers to a deliberate checkpoint in an automation, where a person examines the result and decides whether processing continues.
It is not an admission of failure nor a temporary stage. On processes with consequences it is an architectural decision that stays in place, exactly like a second signature on a transfer.
Where to put it
| Approval needed | Approval pointless |
|---|---|
| Sending a message to a customer | Filing an email |
| Publishing content | Preparing a draft |
| Triggering a payment | Calculating an amount to display |
| Deleting data | Copying data |
| Replying to a public review | Drafting a pending reply |
The rule that emerges: what is reversible can run alone, what is irreversible deserves a look. A badly written draft can be fixed, a sent email cannot be recalled.
The arrangement that works best in practice: the automation prepares everything, the person only has to approve. You keep control without redoing the work, and approval takes five seconds instead of five minutes.
What makes approval fail
Too many requests. Someone asked to approve forty things a day approves everything without looking within a week. Approval that becomes a reflex protects nothing.
Not enough context. "Approve this action?" without showing what is about to go out does not allow a decision. Always display the exact content and what happens next.
No deadline. What happens if nobody approves for three days? Without an answer to that, you will one day discover a queue of two hundred items.
A single approver. That person goes on holiday and the whole chain stops. Plan a substitute, or an explicit fallback rule.
Beware of token approval: presenting ten generated proposals with an "approve all" button is not a control. If the volume makes review impossible, it is the volume that must come down, not the control that must go.
Frequently asked questions
Should approval stay forever?
On irreversible actions, yes. On the others you can remove it once the statistics justify it: if you approve a hundred times in a row without ever correcting, the control is only slowing you down.
How do you set it up in practice?
Every automation tool offers a wait-with-notification step, often by message or email with two buttons. No development is needed.
Does it slow things down much?
Not if the automation prepared everything. The time spent is on review, not execution, and it is counted in seconds when the presentation is well made.
Where do you place this checkpoint in a real project?
Just before the first action that leaves your business, working back up the chain from the end. Our n8n course applies that check to every scenario built, before it ever goes live.