Resources · Make integration

Sensibot.io Make integrationAutomate Sensibot.io with Make.

Can Make send your WhatsApp messages through Sensibot.io for you? The Sensibot.io Make integration gives you 5 modules: 1 trigger and 4 actions. This guide links your account, builds a first scenario and explains when each module fits.

Try the Sensibot.io integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Sensibot.io Make integration let you automate?

The Sensibot.io Make integration links your Sensibot.io account to Make so that messages go out, or get picked up, without anyone copying text by hand. You build a scenario, the automation made of modules chained together, and Make runs it on a schedule or when another app hands it an event.

Confirm an order on WhatsApp. An online store can start a scenario from its shop app and end it with Send a WhatsApp Template Message, so the buyer hears back without a support agent typing anything.

Log every incoming conversation. Watch New Messages picks up new messages on the scenario's schedule and passes each one as a bundle, one item handed from module to module, to a spreadsheet or a CRM of your choice.

Reach an endpoint the list does not cover. Make an API Call reuses your connection to call any endpoint of the Sensibot.io API when the four ready-made actions fall short.

Be aware that Make's documentation for this app is thin: it says there is not enough public information about Sensibot.io to describe every module in detail, so test each field with Run once before relying on it. The same app may also exist as an n8n node; the n8n vs Make comparison lays out the two tools side by side. To go further, see our Make review or the Make training.

Connect

How do you connect Sensibot.io to Make?

  1. 01

    Add a Sensibot.io module

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

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, for example the brand or number it serves. Then follow what Make shows: either approve access on the Sensibot.io page, or paste the key that Sensibot.io gives you.

  3. 03

    Save and check the result

    Click Save. The connection now appears in the module's dropdown, and any other Sensibot.io module in any scenario can pick it without asking you to log in again.

First scenario

Your first scenario with Sensibot.io

GoalWhen a new order lands in your shop app, Make sends the buyer a WhatsApp template message through Sensibot.io.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + to add the first module. Here it is the trigger of your shop app, the one that sees new orders.

  2. 02

    Add the Sensibot.io action

    Click the + on the right of the shop module, search for Sensibot.io and pick Send a WhatsApp Template Message. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the order data

    Fill the module's fields by mapping values from the shop module, such as the buyer's phone number or name. Make shows what it can read once the connection exists, so you rarely type anything by hand.

  4. 04

    Test with Run once

    Click Run once, then place a test order. Open the bubbles above each module to read the bundles it received and confirm the message reached your own test phone.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on, and each new order is handled without you.

Triggers

What starts a Sensibot.io scenario

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

Sensibot.io1Watch New Messages

Watch New Messages

triggerIn the docs only

This trigger hands your scenario each new Sensibot.io message as its own bundle, so the rest of the flow can file it, forward it or answer it without anyone watching the inbox.

How it fires
scheduled, Make checks the app on the scenario's schedule. The type comes from the module's name, since Make's documentation gives no description, so look for the clock badge on the module in your editor.
When to use it
you want every incoming conversation copied into a spreadsheet or a CRM record as soon as the next run picks it up.
Watch out
if the same scenario replies through Sensibot.io, test with Run once that your reply is not picked up again as a new message.
Modules

What the Sensibot.io modules can do

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

Sensibot.io1

Make an API Call

ActionIn the docs only

This module gives you access to any endpoint of the Sensibot.io API from inside a scenario, using the connection you already created, so you are not stuck when the ready-made actions miss a feature.

When to use it
the Sensibot.io API offers something that Send a Message and the two WhatsApp actions do not.
Watch out
you write the request yourself, so keep the Sensibot.io API documentation open next to you.
Sensibot.io2

Send a Message

ActionIn the docs only

Your scenario gets a way to post a message through Sensibot.io at the end of a flow, driven by data from earlier modules instead of text typed by hand.

When to use it
a support ticket changes status in your helpdesk and the customer should hear about it straight away in their chat.
Watch out
the documentation does not list its fields, so run the scenario once and read the bundle before going live.
Sensibot.io3

Send a WhatsApp Template Message

ActionIn the docs only

With this action, a WhatsApp template message goes out through Sensibot.io, so each contact receives a message built on the same model, filled with their own data from the scenario.

When to use it
a booking or a payment is confirmed in another app, and the same confirmation wording should reach every customer.
Watch out
pick the template and test on your own number first, since Make's documentation describes none of its options.
Sensibot.io4

Send a Whatsapp Cloud Message

ActionIn the docs only

Here you get a second WhatsApp path: the module name points to WhatsApp Cloud, and with it your scenario sends a message that way through your Sensibot.io account.

When to use it
your Sensibot.io setup runs on WhatsApp Cloud and you want that channel rather than the generic Send a Message action.
Watch out
the documentation does not explain how it differs from the other send modules, so compare them with Run once on a test contact.
Need help

Need help automating Sensibot.io with Make?

A person reads every message.

FAQ

Sensibot.io and Make: frequent questions

01Is the Sensibot.io Make integration free?
Yes, Sensibot.io is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution 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. Make counts usage in credits, meaning operations, per month. Your Sensibot.io subscription is a separate matter that this page does not cover.
02What do you need to connect Sensibot.io to Make?
You need a Sensibot.io account and a Make account. Make's documentation lists no specific prerequisite for this app and describes only the generic steps: add a Sensibot.io module, click Create a connection, name it if you wish, authorize Make on the Sensibot.io page or paste the key Sensibot.io provides, then click Save. The connection is then reused by all five Sensibot.io modules. If you are unsure which key to use, Sensibot.io support is the right place to ask.
03Does the Sensibot.io trigger in Make work in real time?
No. Watch New Messages is listed as a scheduled trigger, a type deduced from its name because the documentation does not describe it. Make checks Sensibot.io on the scenario's schedule, every 15 minutes by default, and never less than 15 minutes apart on the Free plan. Paid plans let you go down to 1 minute. New messages therefore reach your scenario at the next check, not the instant they arrive, which is fine for logging but worth knowing before you promise instant replies.
04What if a Sensibot.io module is missing in Make?
Use Make an API Call. With the same connection, it can reach any endpoint of the Sensibot.io API from your scenario, which covers what the four other modules do not. Keep in mind that Make's own documentation for this app is limited: it states there is not enough public information about Sensibot.io to write detailed guides. That makes the Sensibot.io API documentation your main reference, and a test with Run once your safety net before switching a scenario on.
05Should you use Make or n8n for Sensibot.io?
It depends on the tool your team already uses. Sensibot.io is available in Make with 5 modules, including a generic API call, and the same app often has an n8n node as well. Neither choice is ranked here: look at which editor your team knows, which other apps your flows touch and how each tool counts usage. If you already build scenarios in Make, staying there keeps every automation in one place. Our comparison page, linked higher up, sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations