Resources · Make integration

HITL Make integrationAutomate HITL with Make.

Need a person to weigh in before your automation moves on? The HITL Make integration gives you 4 modules: 1 trigger that watches for responses and 3 actions. This guide walks you from the API key to a first working scenario.

Try the HITL integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HITL Make integration do for you?

The HITL Make integration links your HITL - Human in the Loop account to Make, so a scenario (the automation you build in Make, a chain of modules) can open requests in HITL, check where they stand and pick up the responses. Make files the app under AI, and it is a standard app, so it works from the Free plan.

Send a request from another tool. Something happens in an app you already use, and Create a Request opens a matching request in HITL. The data you map from the first module becomes the content of that request.

Act on the answer. Watch for Responses starts a scenario each time HITL has a new response to hand over. From there you add whatever should follow: update a record, notify a teammate, file the result.

Check a request later. Get a Request Status reads the current state of one request, handy in a flow that has to know whether it has moved before going further.

The official doc stays short: it lists these modules without fields or limits, and it warns that its own text was generated from vendor material and may contain mistakes. Anything the modules leave out goes through Make an API Call. If you are still choosing a tool, read our n8n vs Make comparison, and the Make pricing guide before you plan volume.

Connect

How do you connect HITL to Make?

  1. 01

    Generate an API key in HITL

    Log in to HITL - Human in the Loop, open the Settings page, go to the API Keys section and click Generate. Copy the key shown on screen right away, since you will paste it into Make in a moment.

  2. 02

    Add a HITL module and open the connection

    In your scenario, add any HITL module and click Create a connection. A connection is your HITL account linked to Make once, then reused by every HITL module you add later. The Connection name field is optional.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the on-screen instructions, and confirm. Make then shows the connection in the module, and you can move on to filling in its fields.

First scenario

Your first scenario with HITL

GoalWhen a new item lands in another app you use, Make opens a request in HITL with its details.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app where the event starts, for example your form tool or your CRM, and choose its trigger module.

  2. 02

    Connect that first app

    Click Create a connection for that app, then fill its fields. Once the connection exists, Make lists the forms, lists or objects it can read, so you pick instead of typing.

  3. 03

    Add Create a Request

    Click the + on the right of the first module, search for HITL and pick Create a Request. Use the HITL connection you set up earlier and map data from the previous module into the request.

  4. 04

    Test with Run once

    Click Run once and trigger a real event in the first app. Each module shows the bundles it received (a bundle is one item passed along), so you can check that the request reached HITL.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What can start a HITL scenario?

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

HITL1Watch for Responses

Watch for Responses

triggerIn the docs only

Watch for Responses is how a HITL answer turns into the next step of your process. Each new response it picks up becomes a bundle that the rest of your scenario can use, so the reply to a request does not sit unread in HITL.

How it fires
the doc does not state its type; going by its name, it is a scheduled trigger, so Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
in a scenario separate from the one that creates requests, to act once someone has responded.
Watch out
it is not instant, so plan for the gap between a response and the next check.
Modules

What can the HITL modules do?

HITL gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

HITL1

Create a Request

ActionIn the docs only

Create a Request opens a new request in HITL from inside your scenario, filled with the data you map from earlier modules. It is the entry point of the loop: nothing reaches HITL until this module runs.

When to use it
right after the event that needs a decision, such as a new form entry or a new deal in your CRM.
Watch out
each run creates one request per bundle, so a trigger that returns several items opens several requests.
HITL2

Get a Request Status

ActionIn the docs only

Get a Request Status gives you the current state of one HITL request, so a scenario can decide what to do based on where that request stands. You point it at a request you created earlier.

When to use it
when a flow must check a specific request before it continues, rather than waiting for a new response to arrive.
Watch out
the doc does not list the possible statuses, so run it once and read the output before you build filters on it.
HITL3

Make an API Call

ActionIn the docs only

Make an API Call lets your scenario reach any endpoint of the HITL API with the connection you already have, so no second login is needed. It covers what the three ready-made modules do not.

When to use it
when you need a HITL feature that has no module of its own in Make.
Watch out
you build the request yourself, so keep the HITL API documentation open and test with Run once first.
Need help

Need help automating HITL with Make?

A person reads every message.

FAQ

Questions about the HITL Make integration

01Is the HITL Make integration free?
Yes on the Make side: HITL is a standard app, so its modules work on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. HITL itself needs an active account, and its own subscription is described on the HITL - Human in the Loop pricing page, not in Make.
02What do you need to connect HITL to Make?
You need an active HITL - Human in the Loop account and an API key. Log in to HITL, open Settings, go to API Keys, click Generate and copy the key. In Make, add a HITL module, click Create a connection, optionally give it a name, then paste the key. The same connection then serves every HITL module in your scenarios, including Make an API Call, so you only go through this once per account.
03Does the HITL Make integration react in real time?
Not as far as the doc shows. It does not state the type of Watch for Responses, but its name points to a scheduled trigger: Make checks HITL for new responses on the scenario's schedule, which is every 15 minutes by default. On the Free plan you cannot go below 15 minutes; paid plans allow an interval of 1 minute. So a response reaches your scenario at the next check, not the moment it is given. If a flow needs to know the state of one request at a precise point, Get a Request Status reads it on demand.
04What if a HITL feature is missing from the Make modules?
Use Make an API Call. It sends a request to any endpoint of the HITL API with the connection you already set up, so it covers what Watch for Responses, Create a Request and Get a Request Status do not. You write the call yourself from the HITL API documentation. Keep in mind that the Make doc for this app lists no fields or limits and notes that its text may contain mistakes, so verify key details with HITL directly.
05Should you use Make or n8n for HITL?
It depends on what you check. In Make, HITL comes with 4 modules: a scheduled trigger, two actions for requests and a generic API call, all available from the Free plan. For n8n, look at whether a HITL node exists before comparing, since this page only covers Make. Then weigh which editor your team already knows and which other apps your flow needs, and test the same small flow in both.
Same platform

Other docs you might need on this stack.

Browse all integrations