Zapier Human Approval Step: 3 Ways to get in the loop

Zapier has had a complicated relationship with approvals. It soft-launched an “Approval by Zapier” beta back in 2020, killed it in February 2023, and told everyone to assemble their own approval flows out of Tables and Interfaces. Then in October 2025 it shipped the real thing: Human in the Loop, a built-in app that pauses a Zap until somebody reviews it. So if you’re searching for how to add a Zapier human approval step in 2026, the answer is genuinely “it’s built in now”, with three native routes to choose from and some plan gates you should know about before you pick one.

This is the third platform in our series, after Make.com (native approvals are Enterprise-only, everyone else builds a two-scenario workaround) and n8n (native everywhere, including the free self-hosted edition). Zapier lands in between: the feature is real and well designed, and the ladder you have to climb to use it properly is very Zapier.

Coming from Relay.app? Here’s the honest trade

Worth pausing on if you landed here because Relay.app is shutting down, free accounts August 15, 2026 and paid accounts September 14. Zapier is the destination Relay users hear about most, and on the approval question specifically it’s the closest match of the three, with a catch that shows up on the invoice and in your reviewers’ inboxes.

The close match is real. Human in the Loop reproduces the thing Relay was actually good at: the reviewer sees the drafted work, edits the parts that are wrong, and approves the corrected version rather than declining the whole run and redoing it by hand. Very few tools do edit-in-the-loop at all. Zapier also brings the largest app catalog of any platform in this series, so the integrations you were using in Relay are more likely to exist here than anywhere else.

The catch is the ladder. In Relay, a human step was just a step, and the free tier gave you one. In Zapier, Human in the Loop is a premium app that starts on the Pro plan, and on Pro you can only send approval requests to yourself. The moment a teammate or a client is the reviewer, you’re on Team or Enterprise. Every reviewer needs a Zapier account and has to log in to answer, which is a real change if your Relay approvals went to somebody who just clicked a link in an email. And each decision counts as a task, so unlike Relay, where the step meter at least treated approvals like any other step, here the safety check has its own line on the meter.

Rebuilding, meanwhile, is not importing. Nothing reads Relay’s format, so each workflow gets translated by hand from the JSON and AI-prompt exports, and you want those files out before your account’s deletion date. If the deadline is closer than your free evenings, send us the export and we’ll rebuild the workflows for you at no cost, then hand back a private link so you can watch them run before deciding anything.

Route 1: Human in the Loop, step by step

Same running example as the other two tutorials so you can compare builds: a customer asks for a refund, your Zap looks up the order and drafts the refund reply, and nothing moves until you’ve looked at it.

Build the front of the Zap as usual: the trigger, the order lookup, the AI step drafting the reply. Then add a Human in the Loop step with the Request Approval event. The minimum configuration:

• Content to review. Field and value pairs, mappable from earlier steps. Put the work in here: order ID, refund amount, and the drafted reply. The reviewer should be judging the actual decision, not clicking blindly.
• Button labels. Approve and Decline by default, customizable if “Refund it” and “Don’t” read better to you.
• Action if reviewer declines. Continue run or Stop run. Choose Continue if you want a decline path that updates your records; choose Stop if a no should simply end the Zap.
• Reviewer editing. A toggle controls whether the reviewer can edit the content before approving. For an AI-drafted reply this earns its keep, since you can fix one clumsy sentence and approve rather than decline the whole run and redo it by hand later.

Next, choose how the request reaches you: email, Slack, or a trigger for a second Zap. That last option is quietly powerful, since the New Approval Requested trigger lets you route approval notifications through any app Zapier connects to.

The reviewer’s side: they get the notification, follow the link, log in to Zapier, and land on a review page showing your message and the content fields. They can edit (if you allowed it), then approve or decline. While the run waits, it shows a “Needs review” status in your Zap history.

After the decision, the run resumes with a Decision field you can branch on with Paths, and any reviewer edits arrive as separate mappable “Edited Content” fields, so your send-the-reply step can use the corrected version. Full setup details live in Zapier’s Request Approval doc.

Timeouts and the no-answer branch

Every approval needs an answer to “what if nobody clicks?” In Zapier, you set a timeout anywhere from one minute to weeks, optionally with reminder notifications before it expires, and you choose what expiry does: Skip and continue (the run proceeds as if waved through, sensible for low-stakes reviews) or End run (silence means no, the right default for anything touching high-risk actions).

One catch to plan around: runs that stop on a decline or timeout can’t be autoreplayed. Your only option is replaying the whole run from the top, and a full replay makes the reviewer re-approve every Human in the Loop step in the Zap. Treat declined runs as finished, not as something you’ll fish back out later.

Route 2: an approvals table

If you’d rather have a queue than an inbox, Zapier Tables has a Button field with a “Continue Zap” type: the Zap runs up to the button step, writes the pending decision as a table row, and waits. One button field can hold two buttons, so a row reads Approve / Reject side by side, and Paths branch on which one was clicked. Zapier’s own approvals table tutorial walks through the exact build.

Two things make this route attractive: button fields work on the Free plan, and tasks executed through Tables buttons don’t count toward task usage. The catch is that sharing a table with teammates requires Team or Enterprise, so as a solo operator you get a tidy private review queue, and the moment a second reviewer enters the picture you’re on the same plan ladder as Route 1.

Route 3: Slack’s Request Approval action

Slack-first reader? The Slack integration has its own Request Approval action (shipped May 2025): the approval message posts to a channel, DM, or thread with Approve and Decline buttons, the Zap pauses, and the decision flows downstream like any other step output. Less configurable than Human in the Loop, but the reviewer never leaves Slack, and for a two-person team living there all day that friction is basically non-existent.

The plan gates and the meter

The launch posts barely mention it, but Human in the Loop is a premium app: Pro plan and up, not available on Free. And on Pro there’s an additional constraint: you can only send approval requests to yourself. Assigning a teammate or a client as reviewer requires Team or Enterprise. Guest reviewers (added December 2025) soften this for external collaborators, but every reviewer, guest or not, needs a Zapier account to respond. Your client approving one refund a week now holds Zapier credentials, and if your org uses domain capture with invite-only membership, external reviewers may not be able to sign up at all.

On billing: each successful Human in the Loop action counts as one task. The waiting costs nothing and notifications are free, but every decision you make adds a tick to the meter, on top of the tasks the rest of the Zap already burns. We’ll leave the full arithmetic of approval-heavy Zaps for another day; for now, just know the approval step itself is billed, which shapes how freely you’ll sprinkle them through your workflows.

Fine print that bites

Smaller traps, collected from the docs so you don’t collect them in production:

• No Human in the Loop inside or after Looping steps. Structure the Zap so the approval happens before any loop, or restructure to avoid the combination.
• Turning a Zap off with approvals pending is undocumented territory. Zapier’s Delay docs say scheduled actions die when a Zap is off, and there’s no published answer for whether pending approvals survive. Assume they don’t, and drain the queue before editing or pausing a Zap.
• The legacy DIY route is unauthenticated. If you find an older tutorial describing two Zaps joined by webhook approve links, know that anyone holding the link can click it, and Webhooks by Zapier is itself a premium app. The native routes above made that pattern obsolete; the login requirement that annoys reviewers is also what makes Human in the Loop materially more secure.

If you’d rather not build the approval page and webhook plumbing yourself, the free Approval Gateway hosts the approval link, the mobile-friendly decision page, and the signed callback for you.

Three platforms, one missing piece

Across the series, a pattern: Make gates approvals behind Enterprise, n8n gives them away but scatters decisions across chat threads, and Zapier built a polished gate that bills per decision and puts a login wall in front of your reviewers. All three share something more fundamental, though. The gate never changes. Your five-hundredth identical approval interrupts you exactly like your first, because none of these platforms learn anything from the five hundred decisions you made.

That’s the gap Rills is built around. Approvals are free, always, so you never weigh a safety check against a meter. Each decision is a permanent record with the full context you saw when you made it, not a boolean in an expiring run log. And confidence scoring puts those decisions to work: actions you reliably approve start clearing on their own, and the queue narrows to the calls that genuinely need you. If you’d rather build the gate once and have it learn, see it in a demo.

Common questions

Is Zapier's Human in the Loop the same as Relay.app's approval step?

It is close in shape and different in cost. Both pause the run and let the reviewer edit the content before approving. The differences are that Human in the Loop is a premium app on the Pro plan and up, every reviewer needs a Zapier account and has to log in to respond, and each decision counts as one task against your usage.

Does adding a human approval step to a Zap cost extra?

Yes, in two ways. Human in the Loop requires the Pro plan or higher, and each successful approval action counts as one task on top of the tasks the rest of the Zap already uses. The waiting itself is free and notifications are free. The Zapier Tables button route avoids the meter, since tasks executed through Tables buttons do not count toward task usage.

Can someone approve a Zap without a Zapier account?

No. Every reviewer, including guest reviewers added in December 2025, needs a Zapier account to respond to an approval request. If your organization uses domain capture with invite-only membership, external reviewers may not be able to sign up at all.

Can I move my Relay.app workflows to Zapier automatically?

No. No platform imports Relay's format, so you rebuild each workflow rather than importing it. Relay's AI-prompt export is the piece that carries over, because it describes each workflow in plain language.

What happens to a pending Zapier approval if I turn the Zap off?

It is undocumented. Zapier's Delay docs say scheduled actions die when a Zap is off, and there is no published answer for pending approvals. Assume they do not survive, and clear the queue before you edit or pause a Zap.