Resources · Make integration

SnatchBot Make integrationAutomate SnatchBot with Make.

What happens to a chatbot message once SnatchBot receives it? The SnatchBot Make integration gives you 1 instant trigger that hands each new message to Make. This page shows support and ops teams how to link the account, build a first scenario and pass messages on.

Try the SnatchBot integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SnatchBot Make integration do?

The SnatchBot Make integration lets a message sent to your SnatchBot chatbot start an automation in Make. A scenario (the automation you build in Make, a chain of modules) begins with Watch Messages, then any other app picks up the message and does something useful with it.

Your support team sees chatbot messages where it already works. Put Watch Messages first, then add the module of your team chat app. Each new message lands in the shared channel, so nobody has to keep the SnatchBot dashboard open.

Every conversation ends up in one place. The same trigger can feed a spreadsheet or a database module, row by row. Each message travels as a bundle (one item passed from one module to the next), so one message becomes one row.

Sales hears about new prospects. A visitor who asks the bot about an offer can become a record in your CRM: put the CRM module right after Watch Messages and map the message into it, so the sales rep starts from what the visitor actually wrote.

Know the limit before you start: SnatchBot has a single module in Make, and Make itself says its documentation for this app is limited because little public information exists. There is no action to send a reply back to the bot from Make. If you want to compare with the other big automation tool, read n8n vs Make. For the basics of the editor, Make training walks through them step by step, and Make pricing explains how operations are counted.

Connect

How do you connect SnatchBot to Make?

  1. 01

    Add the SnatchBot module

    In a new scenario, click the +, search for SnatchBot and pick Watch Messages. Then click Create a connection. A connection is your SnatchBot account linked to Make once, reused by every SnatchBot module afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the bot it serves; this part is optional. Then either approve Make on the SnatchBot page that opens, or paste the key SnatchBot gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. The connection now appears in the module settings, and you can finish configuring Watch Messages. If the module opens without errors, Make can talk to your SnatchBot account.

First scenario

Your first scenario with SnatchBot

GoalWhen a visitor writes to your SnatchBot chatbot, Make sends the message to the tool your team reads.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Place Watch Messages

    Search for SnatchBot, pick Watch Messages and select your connection. It shows a lightning badge: SnatchBot calls Make as soon as a message comes in.

  3. 03

    Add where messages go

    Click the + on the right of Watch Messages and add the module of the app your team reads. Map the message data coming from SnatchBot into its fields.

  4. 04

    Test with Run once

    Click Run once, then send a test message to your chatbot. Open the bubble above each module to read the bundles it received and check the text arrived.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, Make waits for SnatchBot to call it instead of checking on the default 15 minute schedule.

Triggers

What can start a SnatchBot scenario?

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

SnatchBot1Watch Messages

Watch Messages

Instant trigger

In Make“Watches for new messages.”

Every new message your chatbot receives becomes a bundle in Make, ready to be forwarded, stored or filtered by the modules you put after it. It is the only SnatchBot module in Make, so every scenario for this app opens here.

How it fires
instant: SnatchBot calls Make through a webhook as soon as a message comes in, so there is no polling interval to set.
When to use it
your team wants to see what visitors ask the bot without logging into SnatchBot.
Watch out
each message counts as operations on your Make plan, and Make offers no SnatchBot action to write back to the bot.
Need help

Need help automating SnatchBot with Make?

A person reads every message.

FAQ

SnatchBot and Make: common questions

01Is the SnatchBot Make integration free?
Yes. SnatchBot is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. The 15 minute minimum interval only matters for scheduled triggers, and Watch Messages is instant. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and count usage in operations per month. Note that this covers Make only; SnatchBot has its own account terms.
02What do you need to connect SnatchBot to Make?
You need a SnatchBot account and a Make account. The Make documentation lists no other prerequisite for this app. Add Watch Messages to a scenario, click Create a connection, optionally name it, then authorize Make on the SnatchBot page or paste the key SnatchBot provides, and click Save. The connection is stored once and reused by any SnatchBot module you add later. Make says its own documentation for SnatchBot is limited, so the account settings in SnatchBot are the place to check if a field is unclear.
03Does the SnatchBot trigger in Make work in real time?
Yes. Watch Messages is an instant trigger, marked with a lightning badge in the editor. SnatchBot calls Make through a webhook as soon as a new message arrives, and the scenario runs right away. That is different from a scheduled trigger, which Make checks on the scenario schedule, every 15 minutes by default. You still need to switch the scenario on after testing it with Run once, otherwise nothing receives the call from SnatchBot.
04What if the SnatchBot module you need is missing in Make?
It depends on what you need. Make offers only one SnatchBot module, Watch Messages, and no Make an API Call module for this app, so you cannot reach other parts of SnatchBot from the same connection. What you can do is send each message to another app that has the actions you want, such as a chat tool, a spreadsheet or a CRM. If the case goes beyond that, the Hackceleration team can look at it with you through the help form on this page.
05Should you use Make or n8n for SnatchBot?
It depends on the tool your team already uses. Many apps also have an n8n node, so check whether SnatchBot has one before choosing. On the Make side, you get one instant trigger for new messages and a visual editor where each step is a module you can test with Run once. Base your choice on the modules each tool offers for SnatchBot and on the other apps your scenario has to reach, not on general claims. The comparison page linked above sets the two tools side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations