Resources · Make integration

Borisbot Make integrationAutomate Borisbot with Make.

Can Make react to what happens in your Borisbot bot? The Borisbot Make integration gives you 3 modules: one trigger and two actions. This page explains what each one is likely for, how to link your account, and how to build a first working flow step by step.

Try the Borisbot integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Borisbot Make integration do?

The Borisbot Make integration links your Borisbot account to Make so a scenario, the automation you build as a chain of bricks, can watch Borisbot and act on it. Each brick is a module: here one trigger, Watch Variables, and two actions, Continue Script and Send Message. No code is needed.

Reply when a value moves. Watch Variables starts the scenario, and Send Message pushes a message back through Borisbot. For a support desk, that could mean following up once a visitor's answer is stored.

Hand the conversation back to the bot. Continue Script, judging by its name, lets a scenario resume a Borisbot script after Make has done its part, such as checking a record in another tool first.

Plug Borisbot into the rest of your stack. Any other app in Make can feed the two actions, so a form entry or a CRM update can end with a Borisbot message.

A limit to know upfront: Make's own documentation says it cannot yet describe Borisbot in full because too little public information exists. Field names and exact behavior are for you to check in the editor. If you are new to the tool, the Make training covers the basics, and the n8n vs Make comparison helps if you are still choosing a platform. For stuck runs, see Make troubleshooting.

Connect

How do you connect Borisbot to Make?

  1. 01

    Add a Borisbot module

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

  2. 02

    Name the connection

    Giving it a name is optional, but it helps when you run several Borisbot accounts or bots. Pick something you will recognize in a list, like the bot or client it belongs to.

  3. 03

    Authorize and save

    Either approve Make on the Borisbot page that opens, or paste the key Borisbot gives you, depending on what the window asks for. Then click Save and the module is ready to configure.

First scenario

Your first scenario with Borisbot

GoalWhen a watched variable changes in Borisbot, Make sends a message through Borisbot.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. The canvas stays empty until you pick one.

  2. 02

    Place the trigger

    Search for Borisbot, choose Watch Variables, then click Create a connection to link your account. Fill in the fields Make shows once the connection works.

  3. 03

    Add the message

    Click the + to the right of the trigger and add Send Message. Map the data coming from Watch Variables into its fields so the message reflects what changed.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles, the items each one received, and confirm the message looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Triggers

What starts a Borisbot scenario

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

Borisbot1Watch Variables

Watch Variables

triggerIn the docs only

This is the only Borisbot module that can open a scenario, so it is where any automation reacting to your bot begins. As its name suggests, it looks at variables in Borisbot and passes what it finds to the next module as bundles.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
you want a follow-up message or an update in another tool once a bot conversation has stored a value.
Watch out
the type is inferred from the module name, since the documentation gives none, so confirm the badge in the editor.
Modules

What Borisbot can do in Make

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

Borisbot1

Continue Script

ActionIn the docs only

You get a way to hand control back to Borisbot at the end of a scenario, so the bot can pick up where it paused. Make gives no official description, and the name is the main clue.

When to use it
Make had to check or fetch something elsewhere before the conversation can go on.
Watch out
test it with Run once on a sample conversation, because its fields are not documented.
Borisbot2

Send Message

ActionIn the docs only

This action puts a message in front of someone through Borisbot, filled with data from earlier modules. It is the natural last brick when a scenario must tell a person something.

When to use it
a variable changed, a form arrived, or a record was updated, and the contact should hear about it.
Watch out
each message sent is one operation on your plan, so a trigger returning many bundles sends many messages.
Need help

Need help automating Borisbot with Make?

A person reads every message.

FAQ

Borisbot and Make: common questions

01Is the Borisbot Make integration free?
Yes. Borisbot is a standard app in Make, so it works 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. 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, one per module per bundle. Borisbot's own pricing is not covered here.
02What do you need to connect Borisbot to Make?
A Borisbot account and a Make account. Make's documentation lists no specific prerequisite for Borisbot and gives no dedicated connection guide, so the generic flow applies: add a Borisbot module, click Create a connection, optionally name it, then either authorize Make on the Borisbot page or paste the key Borisbot provides, and click Save. The connection is then reused by all three Borisbot modules. If the window asks for something you cannot find, look in your Borisbot account settings first.
03Does the Borisbot trigger in Make run in real time?
No. Watch Variables is listed as a scheduled trigger, not an instant one, which means Make checks Borisbot on the scenario's schedule instead of being notified by a webhook. A new scenario runs every 15 minutes by default; on the Free plan that is also the shortest interval, while paid plans can go down to 1 minute. Note that this type comes from the module name, since the documentation does not state it, so check for the clock badge on the module in the editor.
04What if a Borisbot module is missing in Make?
It depends on what you need. Borisbot offers only 3 modules in Make and no Make an API Call module, so there is no generic way to reach other parts of the Borisbot API from Make. Make's documentation also says it cannot describe Borisbot in full for lack of public information. If a step is missing, you can often handle it with another app in the same scenario and let Borisbot send the final message. For a trickier case, the team can look at your setup with you.
05Should you use Make or n8n for Borisbot?
It depends on the platform you already run. Make offers Borisbot as a standard app with one scheduled trigger and two actions, usable from the Free plan and built visually in the scenario editor. Apps in Make often have an n8n node as well, but this page does not rank the two tools or compare their cost. The practical move is to check which platform already hosts your other automations, then confirm the modules you need exist there before you start building.
Same platform

Other docs you might need on this stack.

Browse all integrations