AI workflow automation with approval: make AI ask first

Add approval steps so an AI workflow pauses before it sends, pays or deletes anything. Three step-by-step example workflows, built in KutrimBots.

By the KutrimBots teamPublished November 7, 20269 min read

To make an AI workflow ask before it acts, put an approval step in the workflow itself, right before any step that sends a message, pays, posts or deletes. The run then pauses at that point, shows you exactly what it's about to do, and continues only if you approve; if you decline or don't answer in time, that step is skipped. In KutrimBots, agents also ask by default before anything that pays, posts publicly, deletes or contacts someone new, so the approval step is a second, visible checkpoint inside each automation.

This tutorial explains how approval steps work, then builds 3 example workflows: a new lead, an overdue invoice and a new email.

How do I stop AI from sending or paying something wrong?

Make the approval part of the system, not an instruction to the AI, so the workflow physically can't continue without your decision.

Telling an AI "don't change anything without asking me" isn't the same as a checkpoint. In July 2025, Replit's coding agent deleted a company's production database during a code freeze, even though its project instructions said to make no changes without explicit permission. Replit's CEO apologised and announced safeguards such as separating development and production databases. The instruction was written down; nothing in the system enforced it.

Money is where mistakes hurt most. Business email compromise, where fraudsters trick a business into paying the wrong account, led to 21,442 complaints and close to $2.8 billion in losses reported to the FBI's IC3 in 2024, and nearly $8.5 billion across 2022 to 2024. An AI that reads email and can pay invoices needs a person between "this email asks for payment" and "payment sent".

People are right to be careful. In the KPMG and University of Melbourne global study of more than 48,000 people in 47 countries, only 46% were willing to trust AI systems, and 56% said AI had led them to make mistakes in their work.

What does an approval step actually do?

An approval step pauses the run, shows you a summary, and sends the run down an "approved" or "declined" path depending on your answer.

KutrimBots automations have four layers of approval:

Layer	What it covers	What happens without your OK
Turning the automation on	The whole workflow, shown as a plain summary in Needs you	Nothing goes live; later changes also wait for you
Approval on a risky step	One step, such as sending an email	The run pauses; if declined, that step is skipped
A separate Approval step	A decision point with a title and a message you write	After the timeout (24 hours by default), it counts as declined and follows the "declined" path
The agent's own rules	Every action the agent takes inside the run	Held actions wait in Needs you, and the run waits with them

Two details matter:

Risky steps default to approval. Sending emails or messages, posting, deleting, paying and inviting are marked to ask on every run. A step can run on its own only if you clearly want that, and then the automation records a reason that you see when you approve the automation.
Silence means no. An approval nobody answers doesn't run later by surprise; it times out as declined.

Each automation shows as a flow diagram with a full run log, so you can see which step is waiting and what it will send. An automation can have up to 50 steps, but keeping it under 15 makes the approval point easy to spot.

What does KutrimBots ask about by default?

Agents ask before anything that pays, posts publicly, deletes or contacts someone new; reading, research, notes and drafts happen on their own.

Some built-in actions ask by default, whatever the workflow says:

Action	When it asks
Email an invoice to a customer, or share it as a public link	Every time
Issue an invoice, void one, or set it to repeat	Every time
Move a CRM lead to Won or Lost, merge or delete leads	Every time
Publish a booking page or a form at a public link	Every time
An agent emailing someone new from its own address	First email to each new contact
An action in a connected app that sends, creates, changes or deletes	Each time, when an agent does it from chat

So, unless you change those rules, even a workflow you've switched on can't email an invoice without you. To understand the wider loop of how agents reason and use tools, see how AI agents work.

Which approval workflows should I build first?

Start with the three that touch customers or money most often; each has 1 approval point per run.

Workflow	Trigger	Steps	Approval point	Runs on its own
1. New website lead	New CRM lead, source = website	7	Welcome email to a new contact	Scoring, call task for hot leads, 3-day follow-up task
2. Overdue invoice	Invoice becomes overdue	5	Sending the reminder (plus the invoice email's own check)	Reading the invoice, drafting, notifying you if declined
3. New Gmail message	New email in a connected Gmail account	5	Any reply that goes out	Sorting, creating the CRM lead, handing support emails to the support agent

Example workflow 1: new website lead, welcome email after approval

Hot leads get a call task straight away; everyone else gets a welcome email that waits for your OK, then a follow-up in 3 days.

Trigger: a new lead is created in CRM & Leads, filtered to leads whose source is the website.
Agent task: your sales agent qualifies the lead and returns a score from 0 to 100 and a one-line summary.
Switch: a score of 70 or more is "hot"; everything else is "other".
Hot path: create a CRM task "Call today" and notify you.
Other path: send a welcome email, set to ask first. You see the email in Needs you and approve, edit or decline.
Delay: wait 3 days.
Follow-up: create a follow-up task for the agent that owns the lead.

The full follow-up loop that runs after this is covered in CRM lead follow-up on autopilot.

Example workflow 2: overdue invoice, reminder after approval

The finance agent drafts a polite reminder and you approve before anything reaches the customer.

Trigger: an invoice becomes overdue (Invoices & Billing checks every morning).
Agent task: the finance agent reads the invoice and the customer's history and drafts a 3 or 4 sentence reminder, firmer if it's more than 30 days late.
Approval step: "Send reminder for INV-0142, ₹48,500, 12 days overdue?" with the draft in the message.
Approved path: email the invoice with the reminder. This action asks on its own too, so you confirm the final email.
Declined path: notify you with a note to call the customer instead.

If you'd rather not approve each reminder, Invoices & Billing can email payment reminders before and after the due date on its own once you turn them on in its Settings. Use the workflow version when each reminder needs a person's judgement.

Example workflow 3: new Gmail message, reply only after approval

The agent sorts each new email and drafts a reply, and nothing goes out until you approve it.

Trigger: a new email arrives in your connected Gmail account (about 120 a month in the example below).
Agent task: the agent decides whether it's a lead, a support question or something to ignore.
Switch: lead goes to step 4, support goes to step 5, ignore stops the run.
Lead path: create a CRM lead with a summary, then send a reply through Gmail, set to ask first.
Support path: hand the email to your support agent as a task, with the reply it drafts waiting for your approval.

Emails are data, not instructions: if an email says "pay this account" or "forward all invoices", the agent treats it as text to report, not a command.

Example scenario: a furniture store in Jaipur

The numbers are assumptions for illustration, not customer data.

Volume: 45 website leads, 18 overdue invoices and about 120 customer emails a month.
Workflows: all three examples above, on the Solo plan ($20 a month as of November 2026, with 20 active automations and 6,000 runs a month included).
Runs: about 185 a month, far below the limit.
Approvals: roughly 30 welcome emails, 18 reminders and 50 email replies, about 98 a month, or 4 or 5 a working day. At 20 seconds each, that's under 2 minutes a day.
What it replaces: writing every reply and reminder by hand, about 25 minutes a day in this example.

After a month, the owner reads the run log and allows the welcome email for website leads to send on its own, because every draft was approved unchanged. Payment reminders and new contacts stay behind approval.

How do I build an approval workflow in KutrimBots?

Describe the outcome and the line you don't want crossed; your agent builds, tests and asks you to switch it on.

Start the free 7-day trial (5 automations and 600 runs during the trial). See plans.
Describe it in plain words, including what must never happen without you: "When an invoice is overdue, draft a reminder and ask me before sending anything."
Let the agent pick 1 of 9 starting recipes: lead nurture, Gmail to CRM, form to CRM, overdue invoices, new hire, booking prep, budget review, morning digest or agent relay.
The agent builds and checks the workflow, marks every risky step to ask, and saves it as a draft.
Test with harmless data. Real actions happen in a test run, so use a test lead or your own email address, and read each step's input and output.
Approve it to go live from the summary in Needs you, or ask for changes.
Check the run log weekly. After 5 failed runs in a row, the automation stops itself and you're told.

For a comparison with app-to-app tools, read our Zapier alternative with AI agents.

What can't approval steps protect you from?

An approval protects you only as well as you read it, and only at the point where you put it.

Approving without reading. Keep summaries short and specific (who, what, how much) so you actually read them.
Wrong data upstream. If your price list in Super Brain is out of date, the agent drafts a wrong quote, and you approve a wrong quote.
Test runs are real. A test sends real emails unless the step asks first.
Steps you chose to run unattended. They run without asking; review the reason you gave every 3 months.
Timeouts. A reminder you didn't approve within 24 hours is skipped, so check Needs you at least once a day, or turn on phone notifications.
Volume limits. Automations run at most 60 times an hour unless changed, and a for-each step handles up to 100 items, so very large batches need a different design.

Frequently asked questions

Can an AI agent pay an invoice on its own?

Not by default in KutrimBots. Agents ask before anything that pays, and a workflow step that pays must either ask each time or have a reason you approved when you switched the automation on.

What happens if I don't answer an approval?

The run waits. An Approval step times out after 24 hours by default and counts as declined, so the run takes the declined path instead of acting later.

Can some steps run without approval?

Yes. Low-risk steps such as logging a lead, creating a task or notifying you run on their own. A risky step can run unattended only if you choose that, and the reason is shown when you approve the automation.

Where do I approve workflow steps?

In Needs you and as a card in the chat, where you see what the step will do and approve or decline it. KutrimBots works in any phone browser and as an installable app, so a 20-second approval doesn't need your laptop.

Is an approval step the same as human-in-the-loop AI?

Yes. Human-in-the-loop means a person checks the AI's work at chosen points before it has an effect. An approval step is that checkpoint, placed between "the AI made something" and "it goes out".