Resources · Make integration

HeroBot Make integrationAutomate HeroBot with Make.

Can Make send HeroBot messages for you when something happens in another app? Yes. The HeroBot Make integration gives you 2 action modules, Send Message and Make an API Call. This page shows how to link your account, build a first scenario and pick the right module.

Try the HeroBot integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HeroBot Make integration do for you?

The HeroBot Make integration links your HeroBot account to Make so that a scenario, the automation you build in Make, can act in HeroBot without code. It has no trigger of its own: another app or a schedule starts the scenario, and HeroBot does the talking at the end of the chain.

Turn a new lead into a message. A form tool fires the scenario when someone fills it in, and Send Message passes the name and request on through HeroBot. The 123FormBuilder Make integration is one way to start that chain.

Confirm a booking on the spot. A scheduling app hands Make the new appointment, and Send Message relays the details. The 10to8 Make integration covers the booking side.

Reach what the listed modules skip. Make an API Call reuses your HeroBot connection to call any endpoint of the HeroBot API, which helps when Send Message does not cover the job.

Know the limit before you start: Make's own documentation for HeroBot is marked as limited, because little public information exists about the app. Expect to check field meanings inside HeroBot itself, and keep the Make troubleshooting guide nearby. The same app often has an n8n node too; the n8n vs Make comparison lays out the criteria to choose between them.

Connect

How do you connect HeroBot to Make?

  1. 01

    Add a HeroBot module

    In your scenario, search for HeroBot and pick a module, for example Send Message. In the module panel, click Create a connection. A connection is your HeroBot account linked to Make once, then reused by every HeroBot module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the workspace or client it belongs to saves confusion later, when several scenarios or several HeroBot accounts share the same Make organization.

  3. 03

    Authorize Make and save

    Either approve Make on the HeroBot page that opens, or paste the key HeroBot gives you, depending on what the window asks for. Then click Save, and the module fields become available.

First scenario

Your first scenario with HeroBot

GoalWhen a new entry arrives in another app, Make sends a message through HeroBot.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since HeroBot has no trigger, this first module belongs to the app where the event starts, such as your form tool.

  2. 02

    Set up the starting app

    Search that app by name, pick its trigger and click Create a connection. Fill its fields; once connected, Make lists the forms, sheets or objects it can read so you pick instead of typing.

  3. 03

    Add Send Message

    Click the + on the right of the first module, search HeroBot and choose Send Message. Connect your account, then map data from the first module, such as a name or a request, into the message.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Each module shows the bundles it received, a bundle being one item passed along, so you can see exactly what reached HeroBot.

  5. 05

    Schedule and switch on

    On the first module, open the clock to set the schedule; a new scenario checks every 15 minutes by default, and 15 minutes is the shortest gap on the Free plan. Then switch the scenario on.

Modules

What HeroBot modules can you use in Make?

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

HeroBot1

Make an API Call

ActionIn the docs only

This module lets your scenario reach any endpoint of the HeroBot API, using the connection you already set up, so you are not limited to what Send Message covers.

When to use it
the moment you need a HeroBot action that has no dedicated module in Make, pick this one instead of looking for a workaround in another app.
Watch out
you need to know the endpoint and what it expects from HeroBot's own reference, because Make's documentation for the app is limited.
HeroBot2

Send Message

ActionIn the docs only

Send Message gets a message out through HeroBot as a step of your scenario, filled with data mapped from the modules before it, like a customer name or an order reference.

When to use it
whenever an event in another app should turn into a HeroBot message, for instance a form reply or a confirmed booking.
Watch out
every message counts as one operation, meaning one run of one module that Make bills on your plan, so each bundle that reaches it costs one.
Need help

Need help automating HeroBot with Make?

A person reads every message.

FAQ

Questions people ask about HeroBot and Make

01Is the HeroBot Make integration free?
Yes, HeroBot is a standard app, so it works from the Free plan. That plan keeps 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes, handles files up to 5 MB and allows 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits, each operation being one module run on one item. This page gives no price for HeroBot itself.
02What do you need to connect HeroBot to Make?
A HeroBot account and a Make account are enough to start, since Make's documentation lists no other prerequisite. Add a HeroBot module, click Create a connection, give it a name if you like, then either authorize Make on the HeroBot page or paste the key HeroBot provides, and click Save. The documentation for this app is marked as limited, so if a value in the connection window is unclear, ask HeroBot for it rather than guessing.
03Does HeroBot trigger Make scenarios in real time?
No, because HeroBot has no trigger module in Make. The scenario starts elsewhere. Use an instant trigger from another app, which calls Make through a webhook as soon as something happens, or run the scenario on a schedule set on its first module, every 15 minutes by default. HeroBot then acts at the end of the chain with Send Message. The speed of the whole scenario depends on how that first module fires, not on HeroBot.
04What if a HeroBot module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the HeroBot API with the connection you already have, which covers actions that Send Message does not. You will need to read HeroBot's own API reference to know the endpoint and the data it expects, because Make's documentation for HeroBot is limited and describes no field. If the action still cannot be done, another app in your scenario may be a better place for that step.
05Should you use Make or n8n for HeroBot?
It depends on your criteria rather than on HeroBot. In Make, the app offers 2 action modules, Send Message and Make an API Call, and no trigger, so another app or a schedule starts each scenario. The same app often has an n8n node as well, so compare what each tool offers for HeroBot, how your team prefers to build, and which other apps you need to connect. Neither choice is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations