Where to put an approval step in a workflow, and who should answer it
An approval step stops a run until a person says yes. Where it belongs, who to ask, how long to wait and what happens when nobody answers, with a worked example.
Part of the guide Location intelligence automation
An approval step in a workflow stops the run at one point until a person says yes. Put it just before the step that cannot be undone, such as sending to people outside the company, creating records in a CRM or telling a crew to act, and after everything that gathers and prepares the work, so the person approving sees the finished result. Then decide three things: who is asked, how long the run waits, and what happens if nobody answers.
Approval is how you let a flow do most of a job on its own while keeping a person on the one decision that matters. This article covers where the step belongs, how to choose the approver and the deadline, approving a whole batch or item by item, a worked example, and the mistakes that turn approvals into a queue nobody clears. For the bigger picture of automating work, see the workflow automation guide.
What deserves an approval
Not every flow needs one. Ask what a wrong run would cost.
- Worth approving: anything that reaches people outside your team (emails and messages to prospects, a plan sent to a crew, a post to a client), anything that changes another system (new deals in a CRM, rows in a shared database), and anything that commits money or people.
- Usually not: a list emailed to yourself, a map, an internal report. If the worst case is a list you delete, let it run.
- Better handled by a rule: checks that are the same every time, such as every lead must have a phone number, are faster as a rule than as a person reading each item.
Where the step goes
Everything before the Approval block runs first; everything after waits. So place it as late as you can: after the data has been found, scored, sorted and written, and just before the block that sends or changes something. The approver then judges the real output, not an early version of it. If a flow has two sending steps of different risk, such as an internal email and an email to customers, put the approval only on the branch to customers.
Who is asked
The block asks the flow's owner, the organization's admins, or members you name by email. Any one of them can answer, and the first answer counts. Name the person who would be blamed if it went wrong, and one deputy for holidays. The people asked get an email with Approve and Decline buttons and a notice in the bell; the approval can also be posted to Slack, Telegram or WhatsApp with the same choice. Each button opens a page that asks to confirm, so a mail program that opens links by itself cannot approve anything.
How long to wait, and what then
Set the wait from how stale the work becomes. A plan for this morning is useless by afternoon; a list of accounts to add to a CRM can wait a few days. When nobody answers in time, the run either stops there, so nothing after it runs, or carries on as if someone had approved. Choose stop for anything that reaches people outside the company. Choose carry on only when sending late is worse than sending unchecked, and when the content is low risk.
The whole batch, or each item
The block approves either all the items together or each item on its own. All together suits one decision about one thing, such as a plan or a report: approve it and everything goes on. Each item on its own suits a list where some items are good and some are not: the page shows a tick box per item, and only the ticked ones go on. With items approved one by one, the approver can also rewrite chosen fields, such as a subject line and a message an AI step drafted, and their words are what gets sent.
A worked example
This example is made up. An events company runs an outdoor product launch in Cape Town. On the morning of the event, the crew needs a weather call by 07:00: go ahead as planned, put up tents, or move indoors. The event manager wants the call written for her, but nothing goes to the crew until she agrees.
- A Schedule runs once, at 06:00 on the event day, in Cape Town's time zone.
- An Area of interest marks the venue, and Weather forecast brings the day hour by hour: temperature, rain and wind.
- An xMap LLM block writes a plan of five lines at most: the call, from what hour, and what to tell guests.
- Approval asks the flow's owner, all items together, with a wait of one day and stop if nobody answers.
- The approved plan goes to the crew on WhatsApp.
At 06:02 the event manager gets the plan on her phone, reads it, and taps Approve. The crew has it by 06:05. Had she disagreed, Decline stops the run there, which is not a failure, and she calls the crew herself. This is the template Event day weather plan, with approval for plan B.
When a question works better than a yes or no
Sometimes the person should choose, not just agree: which of three sites to visit, how many staff to send. The Ask a person block asks a question by email, WhatsApp or Slack, waits for the answer, and carries on with it, so the flow uses the choice. Use Approval for yes or no on finished work, and Ask a person when the answer changes what happens next.
Mistakes that clog approvals
- Approving too early. An approval before the AI step writes means the approver signs off on something they have not seen.
- Too many approvers. When five people are asked, each assumes another will answer. Name one, and one deputy.
- Carry on by default. If the run carries on when nobody answers, the approval is a suggestion. Use stop for anything external.
- Approving what a rule could check. If the approver only ever checks that each item has a phone number, a Filter or Check the work does it without waiting.
- A batch of fifty to read. Long lists get rubber-stamped. Sort and limit to the best ten before the approval.
Who was asked and what they answered stays in the run's history and the organization's activity log. More in Approve before anything goes out; a full prospecting flow with an approval before sending is the template Full outbound engine: find, research, approve, send.
Questions
What happens if nobody approves?
You choose: the run stops at the block and nothing after it is sent, or it carries on as if approved. Stop is the safe choice for anything external.
Can someone approve from their phone?
Yes. The email has Approve and Decline buttons, and the request can also be posted to Slack, Telegram or WhatsApp.
Can the approver change the text before it is sent?
Yes, when items are approved one by one: you choose fields, such as a subject and a message, that the approver can rewrite for each item.
Does a test run wait for approval?
No. A test run goes straight through and says who a real run would ask. Only real runs stop and wait.
Templates that do this
Read next
More on business and places data · Every article · Templates