Add Human Approval Steps Before Risky Actions
A human approval step pauses the workflow until a person says yes or no. It lets you use AI for drafts while a person stays responsible for what goes out. In this lesson you add approval before the project sends a reply.
What You'll Learn
- Which actions need a person and which do not
- How to build an approval step in n8n
- What to do when nobody answers
- How to set up the same step in Zapier and Make
Decide What Needs a Person
Approval costs time. If you approve everything, people stop reading and click yes by habit. Use two questions: how bad is a mistake, and can you undo it?
Save human attention for actions that are harmful and hard to undo.
| Criteria | Easy to undo | Hard to undo |
|---|---|---|
| Small harm | Automate it. Example: add a label to a ticket | Automate it, then check samples. Example: a routine order update |
| Large harm | Approve or review often. Example: change a customer's plan | Always approve. Example: issue a refund, email every customer |
Easy to undo
- Small harm
- Automate it. Example: add a label to a ticket
- Large harm
- Approve or review often. Example: change a customer's plan
Hard to undo
- Small harm
- Automate it, then check samples. Example: a routine order update
- Large harm
- Always approve. Example: issue a refund, email every customer
For the project, a reply to a customer cannot be unsent. So it gets an approval step, at least until you have enough evidence to relax this rule.
Build It in n8n
Many n8n message nodes, including Gmail, Slack, Telegram and Microsoft Teams, have an operation called Send and Wait for Approval. The node sends a message with buttons, then the workflow pauses until someone responds.
- AI drafts the replyDraft and customer summary are ready
- Send and WaitReviewer gets the draft and buttons
- IF: approved?Reads the button result
- Yes: sendThe customer gets the reply
- No: hand overA person writes the reply
Set it up like this:
- Add a Slack or Gmail node after the draft step.
- Choose the Send and Wait for Approval operation.
- Put the customer's message, the AI summary and the draft in the message. The reviewer needs all of it on one screen.
- Change the approval type from Approve Only to Approve and Disapprove, so "no" is a real choice.
- Set Limit Wait Time.
- Add an IF node after it. Run a test, click a button and use the result you see in the output panel.
The Send and Wait operation suits simple yes or no decisions. If you need a more complex response, the n8n docs point to the Wait node, which can resume through a form or a link.
Plan for No Answer
People go on leave and messages get missed. Without a time limit, a waiting run can sit for a long time, and the customer gets nothing.
Choose a rule for every approval step:
Never let an action with a high risk go ahead because of a timeout.
| Criteria | When to use it |
|---|---|
| Remind, then send to a backup person | Most customer-facing work |
| Stop and log it | Risky actions, such as payments |
| Continue anyway | Low-risk actions only, and only if you accept the mistake |
When to use it
- Remind, then send to a backup person
- Most customer-facing work
- Stop and log it
- Risky actions, such as payments
- Continue anyway
- Low-risk actions only, and only if you accept the mistake
When the time limit passes, check what your node returns and add a path for that case. Test it by setting a limit of one minute and not clicking anything.
Make Reviews Fast
A good review message answers these questions in a few seconds:
- What will happen if I approve?
- Who is affected?
- What did the AI use to decide?
- What is the confidence or risk level?
You can use AI to prepare the review note. Try this.
Look at the sample. The record shows one charge, but the draft promises a refund. A good note makes this kind of conflict easy to see.
Learn From the Decisions
Log each decision: the draft, the result, and whether the reviewer rejected it. After a few weeks, you will know how often the AI gets it right for each category. You may then remove approval for one safe category and keep it for the others. Make these changes one category at a time.
In Zapier and Make
Zapier has a built-in tool called Human in the Loop, on paid plans. Its Request Approval action pauses the Zap and lets reviewers approve, decline or edit data. It can notify reviewers by email or Slack. You set a timeout and choose Skip and continue or End run if nobody responds. Choose End run for risky steps.
Make guides describe placing a human review step between the AI output and the action. The features here change often, so check the Make help center. A pattern that works with any tool is to send the draft with an approve link, save the draft in a data store, and let a second scenario continue when the link is clicked.
Key Takeaways
- Use approval when a mistake is harmful and hard to undo.
- In n8n, use the Send and Wait for Approval operation, followed by an IF node.
- Always set a time limit and a path for no answer.
- Show the reviewer everything needed to decide on one screen.
- Log decisions, so you can remove approval later based on evidence.
Quiz
Up next · Lesson 5 of 7
Give Your Workflow Memory and Data Lookups
4 min read
4 of 7 lessons done