Human in the Loop Zapier integrationAutomate Human in the Loop with Zapier.
The Human in the Loop Zapier integration gives you 1 trigger, 2 actions and 0 searches. It holds a Zap until a person approves, corrects or completes the data, then lets the run continue. It is a premium app, so plan on a paid Zapier plan.
Premium app Zapier reserves this app to its paid plans.
Verified Trustpilot reviews · AI, automation & growth agency
What the Human in the Loop Zapier integration actually does
Human in the Loop is Zapier's built-in way to stop an automation halfway and hand it to a person. One step asks someone to sign off on content or to type in what is missing. The run waits for that answer, then carries on with whatever the reviewer decided.
Three things come out of it. First, an approved draft: Request Approval shows a reviewer the content, and if you allow it they can fix a typo before saying yes. Second, a completed record: Collect Data asks for the fields your automation cannot guess, like a budget code or a delivery date, and passes the answers to the next steps. Third, an alert sent your way: when a request goes out through the option called Trigger a Zap, New Approval Requested starts a separate Zap that can post to Slack, send an email or log the request wherever your team works.
Now the limits. There is no search step, so a Zap cannot look up an old approval. There are only three operations, all built around one pause. And none of it runs on a free plan, because the app is premium.
Every request also carries a deadline. You set a timeout from one minute up, in minutes, hours or days, and you decide whether the Zap skips the step or stops when nobody answers (which beats a run frozen forever).
Weighing your options? The Human in the Loop Make integration covers the same app on another platform.
Zapier words, explained once
Eight terms you will meet on this page and in the editor. Read them once, the rest makes sense.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
- Task
- The unit Zapier bills. One task equals one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger calls Zapier itself the moment the event happens, so nothing waits.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app. This app has none, which is why old approvals cannot be found.
- Connection
- Your account on an app, linked to Zapier one time and then reused by every step that relies on that app.
What a Human in the Loop Zap costs you
The trigger never costs a task. Each action that succeeds counts as one, and an action that fails costs nothing.
- Free plan100 tasks a month, two-step Zaps only, no premium apps
- This appPremium: paid plan or free trial
- TriggerInstant, costs no task
This app is premium, so the free plan is out: you need a paid plan or the free trial. Keep the arithmetic in mind too. A Zap with a trigger, an approval step and a follow-up action uses two tasks per run. Adding a filter or a second action turns any Zap into a multi-step Zap, which is a paid feature anyway. The interval grid below only matters for polling triggers. New Approval Requested is instant, so it ignores it.
Connect Human in the Loop to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps. That is where every connection lives, and where you can check later which account a step is using. Make sure you have access to anything the Zap will touch that you do not own.
- 02
Add the connection
Click + Add connection, type Human in the Loop in the search box of the dialog and pick it from the results. Then confirm with Add connection to move on to the sign-in.
- 03
Sign in and grant access
Log in to the account in the tab that opens, then allow Zapier to use it. From then on, every Human in the Loop step in your Zaps reuses that same connection.
Your first Zap: a Slack alert for every pending approval
GoalA content team wants a message in its Slack channel each time a blog draft waits for sign-off, plus a row in a tracking sheet.
- 01
Prepare the approval step
In the Zap that produces the drafts, set the Request Approval step to send its request through Trigger a Zap. That choice is what lets a second Zap handle the notification.
- 02
Build the notification Zap
Create a new Zap, pick Human in the Loop as the app and New Approval Requested as the event. Tell it which approval step to listen to.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent items from the connected account, so you map fields on a real request rather than a guess.
- 04
Add Slack, then Google Sheets
Add Send Channel Message, choose the channel and drop the values from the test into the message. Then add Create Spreadsheet Row to log each request.
- 05
Test each step, then publish
Run each action once and read what came back. When the message and the row look right, click Publish to switch the Zap on.
The Human in the Loop trigger
1 event starts a Zap when something happens in Human in the Loop, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Approval Requested
Instant triggerIn Zapier“Triggers when a specific Human in the Loop step runs in another Zap.”
This one starts a Zap whenever a chosen Human in the Loop step begins its work inside another Zap. In practice it pairs with the Trigger a Zap option of both actions: the first Zap pauses, this second Zap tells the right person that something waits for them, in the tool they actually read.
Human in the Loop actions
Human in the Loop gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Collect Data
ActionIn Zapier“Ask for additional information during the Zap run.”
Your Zap stops and asks a person for information it cannot work out alone. You choose the input fields they fill in, and their answers feed the steps further down.
Request Approval
ActionIn Zapier“Ask someone to approve or change data before continuing the Zap.”
Here a reviewer reads the content and says yes or no before the run continues. Set the edit option to Yes and they can also correct it first. You decide what happens on a refusal.
Where a Human in the Loop Zap breaks
Zapier attaches no help article to this app and lists no limit of its own. What breaks comes from Zapier itself, and from the way you set the review.
Four cases come up often enough to plan for before you publish anything. If yours is not among them, the Zapier troubleshooting guide helps you trace it.
Nothing from before the Zap goes on
A Zap only reacts to what happens after you switch it on. Requests created earlier never start New Approval Requested, so moving a backlog is a separate job.A reviewer who never answers
A paused run waits until the timeout you set, then skips the step or stops. Pick the outcome by what a missing answer should mean, and set the one reminder early.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches starts again and again. It burns through your task count fast, so keep the notification Zap free of approval steps.A sudden flood of requests
When a trigger returns a huge batch at once, after a bulk import for example, Zapier's flood protection can hold the runs back instead of firing them all.
Need help automating Human in the Loop with Zapier?
A person reads every message.
