Approval gate
Approve before it goes out
The automation prepares a quote, a customer reply or a payment, then stops. Nothing is sent until someone approves it — by email, in Slack, in Teams or in the CRM.
Our approach · human in the loop
Human in the loop — AI prepares, people decide
Human in the loop (HITL) is a way of designing automations and AI agents where the system does the repetitive work and a person approves decisions about money, customers and people. It’s the principle behind every project at the AutomationNex studio.
Definition
What is human in the loop in process automation?
Full automation is tempting: the process runs on its own and nobody has to touch it. In practice, the most expensive mistakes happen exactly where a system makes a decision no one saw — sending a quote with the wrong price, rejecting a request from a key customer or posting an invoice to the wrong account.
Human in the loop solves this without giving up on automation. Technology does what it does best: it pulls data from your systems, organizes and classifies it, and prepares a ready-to-use proposal. A person gets the case with full context and makes the call — often with a single click. Accountability stays where it belongs: with your team.
This isn’t a lack of trust in AI. It’s a deliberate division of labor: the machine takes over the routine, and people keep the judgment language models don’t have — knowledge of the customer, the context of the business and responsibility for the outcome.
Patterns
Six human-in-the-loop patterns we use in our projects
We match them to the risk of each process. Not every decision needs approval — too many clicks wear a team down just as much as manual work.
Confidence threshold
Escalation when AI isn’t sure
The model scores how confident it is in its classification. Clear-cut cases move on automatically; ambiguous ones go to a person with a note on what’s missing.
Exception queue
People only get the hard cases
An invoice without a PO number, a customer not in the database, an amount over the limit — exceptions land in a single queue with context attached instead of getting lost in an inbox.
Spot checks
Regular review of results
Where approving every case would be overkill, the team reviews a random sample of results. That way you see early when quality starts to slip.
Feedback loop
Corrections teach the system
Every correction a person makes is recorded. We use it to refine rules, prompts and thresholds — so over time the automation needs less and less intervention.
Decision trail
You know who decided and why
The log shows what the AI prepared, who approved the decision and when. That’s the basis for audits, accountability and a calm conversation when something goes wrong.
Where people decide
Which decisions in a process should always be approved by a person?
We agree on this with your team during the audit. Most often, these are decisions that:
Everything else — re-keying data, sorting, reminders, reports — can run automatically, with monitoring and alerts.
- commit the company financially — payments, discounts, quotes above a threshold,
- reach a customer about their individual case — complaints, refusals, exceptions to your terms,
- concern people — hiring, performance reviews, changes to roles,
- have legal or tax consequences — contracts, booking unusual documents,
- can’t be undone — deleting data, canceling an order, sending to your entire list.
How we design it
How we implement human in the loop in n8n and AI agents
-
01
Decision map
We break the process down step by step and mark where decisions are made, who owns them and what an error would cost.
-
02
Approval points and thresholds
For each decision we choose a pattern: an approval gate, a confidence threshold, an exception queue or spot checks.
-
03
Approval where your team already works
In n8n, the workflow waits for a person’s response — by email, in a messaging app or in the CRM — and continues only once a decision is made. No new dashboard to learn.
-
04
Measurement and tuning
We track how many cases need intervention and how many corrections the team makes. We tune the thresholds so there are as many approvals as needed — and no more.
Team well-being
Human in the loop and employee well-being
People accept automation more readily when they see it doesn’t take away their influence over their work. Clear approval points show the team that they make the decisions and AI is a tool — not a competitor. That reduces anxiety about change and resistance to new tools.
It works the other way, too: poorly designed oversight is exhausting. When someone has to approve hundreds of obvious cases a day, they stop reading them and click “approve” on autopilot. That’s why we set thresholds so that people only get the cases where their judgment actually makes a difference.
For larger changes, a psychologist who works with us joins the project — checking the team’s mood and workload before and after rollout. Learn more in the Team change service.
FAQ
Human in the loop — frequently asked questions
What does human in the loop mean?
Human in the loop means that a process run by automation or AI includes points where a person makes or approves the decision. The system prepares a proposal, and a person approves, edits or rejects it.
Doesn’t human in the loop slow automation down?
Not if the approval points are chosen well. Routine cases go through automatically, and people only get the ones where the decision matters — with context attached, so approval takes seconds instead of minutes of manual work.
How is human in the loop different from human on the loop?
With human in the loop, a person approves a decision before it’s carried out. With human on the loop, the system runs on its own while a person monitors it and can step in. We often combine the two: approval for risky decisions, monitoring and alerts for everything else.
Does the EU AI Act require human in the loop?
Article 14 of the EU AI Act requires effective human oversight of high-risk AI systems (for example in recruitment or credit scoring). Most business automations aren’t high-risk systems, but human oversight of important decisions is good practice and evidence of due diligence.
How do you build human in the loop in n8n?
n8n can pause a workflow and wait for a person’s response — for example, by sending a message with “approve” and “reject” buttons by email or in a messaging app — and then continue based on the decision. We design these gates together with a decision log and a reminder when an approval has been waiting too long.
Can an AI agent work without oversight?
It can handle low-risk tasks on its own, such as looking up information or preparing a draft. Actions with external consequences — sending something to a customer, making a payment, changing data in a system — we design with human approval or within strict limits.
Related
Where we apply this approach
Services
AI agents, chatbots and voicebots
Assistants that answer, analyze and prepare decisions — with a human in the loop.
Learn moreServices
Process automation and n8n
n8n workflows and CRM, ERP and API integrations — no more retyping data by hand.
Learn moreServices
Team change
Employee well-being, change communication and support for managers during AI adoption.
Learn moreAutomation under control
Let’s design a process where AI does the work and you make the calls
In a free consultation, we’ll show you which steps can run on their own and where it’s worth leaving the decision to a person.