Resources · Make integration

ChatBot Make integrationAutomate ChatBot with Make.

Can a chat message start work in your other tools on its own? The ChatBot Make integration gives you 12 modules: 1 instant trigger, 9 actions and 2 searches. This guide is for support and ops teams who run ChatBot, and it walks you from the connection to a first working scenario.

Try the ChatBot integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ChatBot Make integration do for you?

It links your ChatBot account to Make so chat activity can drive actions without code. In Make, you build a scenario (the automation itself, a chain of bricks called modules), and the ChatBot modules either listen for a message or act on your users and stories.

Moderate a chat from one keyword. Watch New Message fires when someone types a specific message, and Ban / Unban a User acts on that sender. A community manager can hand the first reaction to Make and review the case afterwards.

Keep your user records tidy. Search Users finds the people you need, Update a User corrects their profile, and Create a User adds someone who signed up elsewhere, for example after a form on your site.

Maintain stories in bulk. List Stories pulls every story of the account, Get a Story opens one by its ID, and Create, Update or Delete a Story change them from a scenario instead of the ChatBot dashboard.

Make only covers what these 12 modules expose. Anything else in the ChatBot API goes through Make an API Call, which reuses the same connection. The same app often exists as an n8n node too; the n8n vs Make comparison helps you pick, and the Make pricing page explains how operations are counted. If a run fails, start with Make troubleshooting.

Connect

How do you connect ChatBot to Make?

  1. 01

    Copy your API token in ChatBot

    You need an active ChatBot account first. Open the developer settings panel in ChatBot and copy the API token shown on screen. Keep it handy, Make will ask for it in a moment.

  2. 02

    Open a ChatBot module in Make

    Log in to Make, add any ChatBot module to your scenario and click Create a connection. A connection is your ChatBot account linked to Make once, then reused by every ChatBot module.

  3. 03

    Paste the token and save

    Give the connection a clear label in Connection name if you like (it is optional), paste the token you copied, and follow the on-screen prompts. Make now lists what it can read from ChatBot.

First scenario

Build your first scenario with ChatBot

GoalWhen a user sends a specific message in a ChatBot chat, Make bans that user automatically.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Add Watch New Message

    Search for ChatBot, pick Watch New Message, click Create a webhook and then Create a connection with your API token.

  3. 03

    Chain Ban / Unban a User

    Click the + on the right of the trigger, choose Ban / Unban a User and map the sender from the trigger's bundle (one message passing to the next module).

  4. 04

    Test with Run once

    Click Run once, then send the watched message from a test chat. Open each module's bubble to read the bundle it received and check the right person was targeted.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, ChatBot calls Make as soon as the message arrives, so there is no polling interval to set here.

Triggers

What starts a ChatBot scenario?

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

ChatBot1Watch New Message

Watch New Message

Instant trigger

In Make“Triggers when a user sends a specific message into a chat.”

This trigger starts your scenario the moment a user types a specific message into a chat, so the phrase itself becomes the switch for everything that follows.

How it fires
instant. ChatBot calls Make through a webhook as soon as the message is sent, and the module shows the lightning badge instead of the clock.
When to use it
a customer writes a keyword such as a refund request or an abuse report, and you want a follow-up handled without anyone watching the inbox.
Watch out
create the webhook before the connection, and remember each message that fires the trigger consumes operations (Make's unit of usage) on every module downstream.
Modules

What can ChatBot do inside a scenario?

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

ChatBot1

Create a User

Action

In Make“Creates a new user.”

Adds a brand new user to your ChatBot account from data collected somewhere else, so the person exists in ChatBot before their first chat.

When to use it
a lead fills in a form on your site and you want their profile ready for the bot.
Watch out
run Search Users first if the person may already exist, or you risk duplicates.
ChatBot2

Get a Story

Action

In Make“Returns details of a story specified by ID.”

Returns the full details of one story when you already know its ID, which gives later modules a clean snapshot to read from.

When to use it
before editing a story, to check its current state or copy its content into a report.
Watch out
without an ID you get nothing; pair it with List Stories when you only know the name.
ChatBot3

Get a User

Action

In Make“Returns details of a user specified by ID.”

Fetches everything ChatBot holds about a single user, identified by their ID, and hands it to the rest of the scenario.

When to use it
a chat event gives you a user ID and you need their profile before deciding what to do next.
Watch out
this module reads only; it changes nothing, so add Update a User if you need an edit.
ChatBot4

Make an API Call

Action

In Make“Performs an arbitrary API call.”

Lets you call any endpoint of the ChatBot API from your scenario, reusing the connection you already created, for jobs the listed modules skip.

When to use it
the ChatBot API offers an operation you need and none of the other 11 modules performs it.
Watch out
you write the request yourself, so keep the vendor documentation open and test with Run once.
ChatBot5

Update a User

Action

In Make“Updates a user specified by ID.”

Changes an existing user's details, picked by ID, so the profile in ChatBot matches what your other tools know.

When to use it
a customer updates their details in your CRM and the bot should greet them with the new information.
Watch out
you need the right ID; fetch it with Search Users when your source only has a name or an email.
ChatBot6

List Stories

Search

In Make“Returns a list of all stories.”

Pulls every story in your ChatBot account and outputs each one as its own bundle, ready to be filtered or copied elsewhere.

When to use it
you want an inventory of your stories in a spreadsheet or need to find one before editing it.
Watch out
as a search, it can return several bundles, and every module after it runs once per story.
ChatBot7

Search Users

Search

In Make“Searches for users or lists them all.”

Finds the users that match your search, or lists all of them, so you can act on the right people without opening the dashboard.

When to use it
before creating or updating someone, to confirm whether they already exist.
Watch out
the result can be zero, one or many bundles; add a filter so the next module only sees the users you mean.
ChatBot8

Ban / Unban a User

ActionIn the docs only

Blocks a user from chatting with your bot, or lifts that block, directly from a scenario so moderation does not wait for a human.

When to use it
right after Watch New Message spots an abusive keyword, or when a support agent clears a case.
Watch out
one module handles both directions, so double check which option you pick before switching the scenario on.
ChatBot9

Create a Story

ActionIn the docs only

Adds a new story to your ChatBot account from Make, so conversation content can be produced by a scenario rather than typed by hand.

When to use it
a new product launches and you keep its script in a document your team edits elsewhere.
Watch out
test on a copy first with Run once, since a new story can change what visitors see.
ChatBot10

Delete a Story

ActionIn the docs only

Removes a story from your ChatBot account, which keeps the bot free of outdated flows once an offer or campaign ends.

When to use it
a promotion is marked as finished in your planning tool and its story should go with it.
Watch out
deletion cannot be undone from Make; run Get a Story first and keep the details somewhere safe.
ChatBot11

Update a Story

ActionIn the docs only

Edits an existing story in place, so a wording or setting change reaches the bot without anyone opening the ChatBot editor.

When to use it
a price or an opening hour changes in your source document and the bot must say the same thing.
Watch out
you target the story by ID, so find it with List Stories when you only know its name.
Need help

Need help automating ChatBot with Make?

A person reads every message.

FAQ

ChatBot and Make: frequent questions

01Is the ChatBot Make integration free?
Yes, on the Make side. ChatBot is a standard app, so its modules are available from the Free plan. That plan allows 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. Your trigger is instant, so the 15 minute interval does not slow it down. Paid plans lift the active scenario limit and bring the minimum interval down to 1 minute. ChatBot itself requires its own subscription, which you manage on the ChatBot side.
02What does the ChatBot Make connection require?
You need an active ChatBot account and its developer access token. In ChatBot, open the developer settings panel and copy the API token displayed there. In Make, add a ChatBot module, click Create a connection, optionally name it, and paste the token. For the Watch New Message trigger, click Create a webhook before creating the connection. After that, every ChatBot module in your scenarios reuses the same connection, so you only paste the token once.
03Does the ChatBot trigger in Make react instantly?
Yes. Watch New Message is an instant trigger: ChatBot calls Make through a webhook as soon as a user sends the watched message, and the module carries the lightning badge. It does not wait for the scenario schedule, which defaults to every 15 minutes for scheduled triggers. That makes it a good fit for moderation or quick replies, as long as the scenario is switched on and the webhook was created along with the connection.
04What if a ChatBot action is missing in Make?
Use Make an API Call. It is part of the 12 ChatBot modules and can reach any endpoint of the ChatBot API with the connection you already have, so you are not limited to the 9 actions and 2 searches listed. You write the request yourself, so check the ChatBot developer documentation for the endpoint. The Make documentation for this app also warns that its text is AI generated from vendor docs, so verify important details with ChatBot directly.
05Make or n8n for ChatBot: which one fits better?
It depends on the tool your team already runs. ChatBot often has an n8n node as well, so both platforms can usually handle the basics. In Make, you get 12 ready modules, an instant trigger on new messages, and Make an API Call for anything else, all behind one connection. If your other automations already live in n8n, check its ChatBot node before splitting your work across two tools. Compare the modules each one offers for your exact use case.
Same platform

Other docs you might need on this stack.

Browse all integrations