Resources · Make integration

Sendbot Make integrationAutomate Sendbot with Make.

Can Make read your Sendbot account without a single line of code? The Sendbot Make integration gives you 4 action modules, all listed under Portuguese names. This guide connects your account, builds a first scenario and tells you plainly what nobody has documented yet.

Try the Sendbot integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Sendbot Make integration let you do?

The Sendbot Make integration links your Sendbot account to Make, so a scenario (the automation you build in Make, a chain of modules) can call Sendbot for you. Sendbot brings 4 modules, all actions: each module is one brick of the scenario, and none of them starts it on its own.

An inventory of your bots. Listar Typebots, Portuguese for List Typebots, is the natural first brick: run it and each typebot your connection can see comes back as a bundle, one item flowing to the next module, ready to be copied into a sheet or a message.

A map of your webhook blocks. Listar Blocos de Webhook plays the same role for webhook blocks. Chained after the first module, it shows which bots carry one, which helps before you plug another tool into a conversation.

A custom request. Faça uma Chamada de API, Portuguese for Make an API Call, is the module to test when the others do not cover your case. Assistir Eventos (bloco de webhook) completes the set.

One limit to know before you start: Make states that it cannot provide complete documentation for Sendbot, for lack of public information. The page therefore describes each module by its name and never invents a field. When a module surprises you, the Make troubleshooting guide helps you read the error, and the n8n vs Make comparison is the place to weigh the two tools on criteria.

Connect

How do you connect your Sendbot account to Make?

  1. 01

    Open the connection window

    Add any Sendbot module to your scenario and click Create a connection. A connection is your Sendbot account linked to Make once; every Sendbot module of every scenario reuses it afterwards.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when you manage more than one account. Then either authorize Make on the Sendbot page that opens, or paste the key Sendbot gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Make now lists what it can read in the module fields. If the list stays empty, the account or the key is the first thing to recheck before touching the scenario.

First scenario

Your first scenario with Sendbot

GoalWhen the scenario runs on its schedule, Make lists your typebots and then the webhook blocks it can read.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Add Listar Typebots

    Search for Sendbot, pick Listar Typebots and click Create a connection to link your account, as described in the section above.

  3. 03

    Chain Listar Blocos de Webhook

    Click the + on the right of the first module, pick Listar Blocos de Webhook and map, when a field asks for it, the data coming from Listar Typebots.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time; open the bubble above each module to read the bundles it received and spot what you can reuse.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Adjust it if needed, then switch the scenario on to let it run by itself.

Modules

What the Sendbot modules do

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

Sendbot1

Assistir Eventos (bloco de webhook)

ActionIn the docs only

Judging by its name, this module lets you follow the events of a Sendbot webhook block from inside Make. Its Portuguese name reads Watch Events (webhook block), yet Make lists it as an action, so it only runs when an earlier step or the schedule reaches it.

When to use it
once a webhook block exists in your bot and you want the scenario to look at what it received.
Watch out
no description exists, so read its output with Run once before building on it.
Sendbot2

Faça uma Chamada de API

ActionIn the docs only

Its name suggests a way to send your own request to Sendbot when the three other modules do not return what you need. The name translates as Make an API Call; Make publishes nothing more about it, fields included.

When to use it
as a last resort, after checking that Listar Typebots and Listar Blocos de Webhook really miss the data.
Watch out
each call is one operation, one execution that Make counts on your plan, so test it on a single bundle first.
Sendbot3

Listar Blocos de Webhook

ActionIn the docs only

You get back the webhook blocks your connection can read, each one as a separate bundle you can pass to the next module. It is the Portuguese label for List Webhook Blocks, and probably the quickest way to spot which of your bots talk to other tools.

When to use it
right after Listar Typebots, to check a bot before wiring it into a wider scenario.
Watch out
a list can come back empty; plan what the scenario should do in that case.
Sendbot4

Listar Typebots

ActionIn the docs only

The result is a list of the typebots visible to your connection, one bundle per bot, which makes it the easiest module to start with. Run it alone and you instantly see whether the connection works and what Sendbot returns.

When to use it
as the first module of any Sendbot scenario, or to copy your bots into a sheet.
Watch out
every typebot becomes its own bundle, so each module placed after it runs once per bot and uses one operation each time.
Need help

Need help automating Sendbot with Make?

A person reads every message.

FAQ

Frequently asked questions about Sendbot and Make

01Is the Sendbot Make integration free?
Yes, Sendbot is a standard app, so it works on the Make Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month, one per module run on one bundle. The price of Sendbot itself is a separate matter between you and Sendbot.
02What is needed to connect Sendbot to Make?
A Sendbot account and a Make account are enough to begin; Make's documentation lists no other prerequisite. Add a Sendbot module, click Create a connection, give it a name if you want, then either authorize Make on the Sendbot page or paste the key Sendbot provides, and click Save. The connection is stored once and every Sendbot module reuses it. If fields stay empty afterwards, check the account or the key first, since the documentation gives no Sendbot-specific troubleshooting to lean on.
03Does the Sendbot Make integration react in real time?
No, not on its own: the 4 Sendbot modules are all actions, and none of them is a trigger that starts a scenario. To launch one anyway, you have two options. Put a scheduled start on the first module, where a new scenario runs every 15 minutes by default, at least 15 minutes apart on the Free plan and 1 minute on paid plans. Or open the scenario with a trigger from another app, including an instant one that the other app calls through a webhook, and place the Sendbot modules after it.
04What if a Sendbot module is missing in Make?
It depends on what is missing. Sendbot has no universal Make an API Call module; its closest cousin, Faça uma Chamada de API, has no published description, so nothing guarantees a way around every gap. Start by testing the four existing modules with Run once and reading their bundles, since Make admits its Sendbot documentation is incomplete and the modules may cover more than their names suggest. If the data still is not there, another app in your scenario may carry it, or the Hack'celeration team can look at the case with you and suggest a route.
05Should Sendbot be automated with Make or n8n?
It depends on your criteria rather than on a winner. On Make, Sendbot offers 4 action modules, a guided connection and a visual editor where the Run once button shows every bundle, which suits a team that wants to test quickly. The same app often has an n8n node too, so check what that node covers before choosing. Compare the modules each tool exposes for your case, the way each one counts executions, and who on the team will maintain the scenario. The comparison page linked above sets out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations