Resources · Make integration

gotoHuman Make integrationAutomate gotoHuman with Make.

Need a person to check something before your automation moves on? The gotoHuman Make integration gives you 3 modules: one trigger and two actions. This guide links your account, builds a first scenario and explains each module in plain words.

Try the gotoHuman integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the gotoHuman Make integration do for you?

The gotoHuman Make integration lets a Make scenario, the automation you build as a chain of modules, send a review request to gotoHuman and then pick up the answer. You get a human checkpoint inside an automated flow, without writing code.

Ask before you act. Data arrives from another app, for example a new lead or a drafted reply. The Create a Review Request module hands it to gotoHuman, based on a review template you set up there, so someone can look at it first.

Act on the answer. Watch the Review Response starts a separate scenario on its next scheduled check after a response comes in. From there, the following modules of other apps do the work that the response calls for.

Reach what the list misses. Make an API Call reuses your gotoHuman connection to call any endpoint of the gotoHuman API, which covers what the two other modules do not.

Keep the limits in mind. The official Make documentation for gotoHuman says it was written with AI help and may contain mistakes, so test every scenario with a real review. If a run fails, the Make troubleshooting guide is a good first stop, and the Make pricing page explains how operations are counted.

Wondering about other tools? The same app often has an n8n node too; the n8n vs Make comparison lays out the differences between the two platforms.

Connect

How do you connect gotoHuman to Make?

  1. 01

    Copy your API key in gotoHuman

    Log in to gotoHuman and open your dashboard. Create or pick a review template, click API Request, choose HTTP as the integration type, and copy the API key that appears on screen.

  2. 02

    Add a gotoHuman module in Make

    In your Make scenario, add any gotoHuman module and click Create a connection. A connection is your gotoHuman account linked to Make once, then reused by every gotoHuman module you add later.

  3. 03

    Name it and paste the key

    Give the connection a name in the Connection name field if you like; it helps when you manage several accounts. Paste the key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with gotoHuman in Make

GoalWhen new data lands in another app, Make sends it to gotoHuman as a review request.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to add the first module. Pick the app whose new data needs a human look, such as your form or CRM tool.

  2. 02

    Set up that first module

    Connect that app and fill its fields. Once the connection exists, Make lists what it can read, so you pick from a list instead of typing names by hand.

  3. 03

    Add Create a Review Request

    Click the + on the right of the first module, search for gotoHuman and choose Create a Review Request. Link your gotoHuman connection and map data from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, like one lead. Then check in gotoHuman that the request arrived.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Adjust it if needed, then switch the scenario on.

Triggers

What triggers a gotoHuman scenario?

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

gotoHuman1Watch the Review Response

Watch the Review Response

triggerIn the docs only

Watch the Review Response hands your scenario the answer given on a gotoHuman review, so the rest of the flow can act on that decision instead of waiting for someone to copy it over.

How it fires
scheduled, a type inferred from the module name since the Make directory was unavailable; the clock badge on the module confirms it. Make checks gotoHuman on the scenario's schedule, every 15 minutes by default.
When to use it
in a second scenario that takes over after the one that sent the request, for example to update a record once a reviewer has answered.
Watch out
a scheduled trigger is not instant, so there is a gap between the response and the scenario run.
Modules

What can gotoHuman do in a Make scenario?

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

gotoHuman1

Create a Review Request

ActionIn the docs only

Create a Review Request puts a piece of data in front of a person in gotoHuman before your automation goes further, so nothing sensitive leaves without a check.

When to use it
right after the module that produces the item to approve, such as a generated text or a new customer record.
Watch out
your API key comes from a review template, so the template likely shapes the request; set it up in gotoHuman before mapping fields.
gotoHuman2

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the gotoHuman API with the connection you already set up, which covers any need the two ready-made modules leave open.

When to use it
when neither Create a Review Request nor the trigger does what your scenario needs.
Watch out
you describe the request yourself, so test it with Run once and read the bundle it returns.
Need help

Need help automating gotoHuman with Make?

A person reads every message.

FAQ

gotoHuman and Make: common questions

01Is the gotoHuman Make integration free?
Yes, on the Make side. gotoHuman is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. You still need your own gotoHuman account; its pricing is set by gotoHuman.
02What do you need to connect gotoHuman to Make?
An active gotoHuman account and an API key. To get the key, log in to gotoHuman, open the dashboard, create or select a review template, click API Request, choose HTTP as the integration type and copy the key shown. In Make, add a gotoHuman module, click Create a connection, optionally fill the Connection name field and paste the key. The connection is then reused by every gotoHuman module in your scenarios.
03Does the gotoHuman Make trigger react in real time?
No. Watch the Review Response is a scheduled trigger, a type inferred from its name, so check for the clock badge in the editor: Make checks gotoHuman on the scenario's schedule rather than being called the moment a response exists. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap; paid plans can go down to 1 minute. Pick an interval that matches how quickly your team needs to act on a decision, and remember that each module execution counts as an operation on your plan.
04What if a gotoHuman module you need is missing in Make?
Use Make an API Call. It reuses your existing gotoHuman connection and can call any endpoint of the gotoHuman API, so it fills the gap left by the two ready-made modules. Keep in mind that the Make documentation for gotoHuman states it was produced with AI help and may contain mistakes, so verify key details directly with gotoHuman and test with Run once before switching the scenario on. That way you see the exact bundles gotoHuman returns.
05Should you use Make or n8n for gotoHuman?
It depends on the platform your team already works in. Make offers 3 gotoHuman modules, a guided editor and a Free plan with 2 active scenarios. The same app often has an n8n node as well, so check what that node covers before you decide. Compare the modules each tool gives you for your use case rather than the brand, and build a small test on the one you pick before moving your real reviews over.
Same platform

Other docs you might need on this stack.

Browse all integrations