Resources · Make integration

Human in the Loop Make integrationAutomate Human in the Loop with Make.

Need a person to approve a step before your automation goes any further? The Human in the Loop Make integration gives you 4 modules for that: 1 trigger, 2 actions and 1 search. It targets Enterprise teams, and this guide takes you from connection to a first working scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Human in the Loop integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Human in the Loop Make integration do for you?

Human in the Loop lets you add a human approval step inside a Make scenario, the automation you build as a chain of modules. You get a checkpoint where a person looks at the item before the rest of the flow runs, which is useful whenever accuracy, compliance or accountability matter more than speed.

An AI draft checked before it reaches a customer. A module from another app writes the text, then Create a review request hands it to a reviewer. Nothing goes out on the automation's word alone.

Decisions picked up without anyone forwarding them. A second scenario opens with Watch completed reviews and receives each finished review as a bundle, meaning one item passed from module to module, ready for whatever comes next.

A clean queue for reviewers. When the original item is dropped, List reviews finds the matching request and Cancel review request withdraws it, so nobody approves something that no longer exists.

Two limits shape everything here: the app is reserved for the Make Enterprise plan, and it is in closed beta, open only to invited customers. The documentation also names the four modules without describing their fields, so the notes below stick to what each module is for. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make training covers scenario basics, and the Make agency can build approval flows with you.

Connect

How do you connect Human in the Loop to Make?

  1. 01

    Add a Human in the Loop module

    In your scenario, click the + and search for Human in the Loop, pick any of its modules, then click Create a connection. A connection is your access to the app, linked to Make one time and reused by every module of that app.

  2. 02

    Give the connection a name

    This step is optional. Type something recognizable in the Connection name field, such as the team or the workspace it belongs to, so you pick the right one later when several connections sit in the same list.

  3. 03

    Save and get back to the module

    Click Save. Make stores the connection and returns you to the module, where you can fill in its settings. Any other Human in the Loop module you add afterwards simply offers this same connection.

First scenario

Your first scenario: get a draft approved by a person

GoalWhen another app produces a draft, Make sends it to Human in the Loop as a review request.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle becomes the first module, the one that starts every run.

  2. 02

    Start from the app that holds your drafts

    Search for the app where the content appears, a help desk or a document tool for example, pick its module and click Create a connection to link that account.

  3. 03

    Add Create a review request

    Click the + on the right of the first module, search for Human in the Loop and choose Create a review request. Map the draft coming from the previous module into its fields.

  4. 04

    Test it with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above each module to read the bundles it received and confirm the draft landed in the review request.

  5. 05

    Schedule it and switch it on

    Click the clock on the first module to set Scheduling, every 15 minutes by default, then switch the scenario on. Each new draft now waits for a human before going further.

Triggers

What starts a Human in the Loop scenario

1 module starts a scenario when something happens in Human in the Loop. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Human in the Loop as soon as it happens.

Human in the Loop1Watch completed reviews

Watch completed reviews

triggerIn the docs only

This trigger lets a scenario pick up reviews a person has finished, at its next check, so the outcome of a review feeds the next steps without anyone copying it by hand. Going by its name, it collects reviews that are complete and hands each one on as a bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the module shows the clock badge.
When to use it
as the opening module of a follow-up scenario that reacts to requests created earlier with Create a review request.
Watch out
the documentation lists this module by name only, and its scheduled type is inferred from that name, so check its fields in the editor before relying on it.
Modules

Every Human in the Loop module, explained

Human in the Loop gives you 3 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

2 modules
Human in the Loop1

Cancel review request

ActionIn the docs only

You free reviewers from requests that have become useless: this action withdraws a review request that no longer needs a human decision. The documentation gives no description, so this reading comes from the module's name.

When to use it
the item under review was deleted or replaced in its source app, and the pending request now points at nothing.
Watch out
an action works on one item at a time, so you need to know which request to cancel, for instance from List reviews.
Human in the Loop2

Create a review request

ActionIn the docs only

Your scenario gains a human checkpoint: this action sends one item to a person for approval before anything else happens to it. It is the module that turns a fully automatic flow into one where someone signs off.

When to use it
right after the module that produces something sensitive, such as a contract draft or an AI reply to a customer.
Watch out
the documentation names the module without listing its fields, so open it once connected to see what Make asks for.

Searches

1 module
Human in the Loop3

List reviews

SearchIn the docs only

You get a view of existing reviews inside your scenario. Like every search module, List reviews can return none, one or several bundles, and the modules placed after it handle each of them in turn.

When to use it
before Cancel review request, to locate the pending request tied to an item that was dropped.
Watch out
with several results, every following module runs once per review, and each run is an operation, the unit Make counts on your plan.
Need help

Need help automating Human in the Loop with Make?

A person reads every message.

FAQ

Human in the Loop and Make: common questions

01Is the Human in the Loop Make integration free?
No. Human in the Loop is an Enterprise app in Make, which means it is reserved for the Enterprise plan and is not part of the Free plan or the standard catalog that every plan includes. On top of that, the documentation says the app is in closed beta and only open to invited customers. You therefore need both the Enterprise plan and an invitation before the modules show up. No price is published for the app itself, so compare Make plans rather than looking for a separate fee.
02What do you need to connect Human in the Loop to Make?
Access to the app on your Make account is the real requirement, since it sits on the Enterprise plan and in a closed beta. The documentation lists no other prerequisite. Once you have access, add any Human in the Loop module to a scenario, click Create a connection, optionally type a Connection name, and click Save. That single connection is then offered to all four modules, so you only go through the steps once per account.
03Does the Human in the Loop trigger react in real time?
No. Watch completed reviews is a scheduled trigger: Make checks the app on the scenario's schedule instead of being notified the moment a review ends. A new scenario checks every 15 minutes by default, and paid plans allow a minimum interval of 1 minute between runs. The documentation lists no instant version of this trigger, so a finished review is picked up at the next check, which is fine for approvals but not for anything that must react on the spot.
04What if a Human in the Loop module you need is missing in Make?
The app has no Make an API Call module, so there is no way to send a custom request to it from Make. You are limited to the four listed modules: one trigger, two actions and one search. When a step falls outside them, handle it with modules from another app in the same scenario, or ask an agency that builds Make scenarios to review your case. Keep in mind the app is still in closed beta, so check the module list in the editor before planning around it.
05Should you use Make or n8n for Human in the Loop?
It depends on where your automations already live. Many apps that exist in Make also have an n8n node, so check whether this one does before deciding. On the Make side the facts are clear: Human in the Loop needs the Enterprise plan and an invitation to the closed beta, and it brings 4 modules for approval steps. This page does not rank the two tools; the comparison linked in the first section sets out the criteria to weigh for your own team.
Same platform

Other docs you might need on this stack.

Browse all integrations