Resources · Make integration

BotStar Make integrationAutomate BotStar with Make.

What happens after your chatbot finishes talking? The BotStar Make integration gives you 4 instant triggers that react to what users do in your bot. This page shows how to link your account, build a first scenario and choose the right trigger.

Try the BotStar integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BotStar Make integration do for your chatbot?

The BotStar Make integration lets conversations in your bot start automations elsewhere. In Make, an automation is called a scenario: a chain of bricks named modules. BotStar brings 4 modules, all instant triggers, which means BotStar calls Make through a webhook as soon as something happens in the bot.

Picture a user who types that they want to speak to a person. With Watch New Request for Human Takeover, that request can land in the tool your support team already watches, instead of waiting in the BotStar inbox until someone looks.

For a marketing team, Watch New Subscriber fires when someone opts in to broadcast messages, so the new contact can be copied into a list or a CRM from another app. Watch New Tag on User works the same way on labels: a sales rep can react to a tag that marks a qualified lead. Watch New Checkpoint Record covers the moments you flag inside a flow.

Know the limits before you start. BotStar in Make only listens: there is no action to send a message, edit a user or add a tag, and no module to call the API directly. Every scenario begins in BotStar and does its work in other apps. Make itself labels its BotStar documentation as AI-generated, so check critical details with BotStar.

New to the platform? The Make training walks through the editor, and Make pricing explains what each plan allows. If you are also weighing another tool, read n8n vs Make.

Connect

How do you connect BotStar to Make?

  1. 01

    Get your BotStar details ready

    You need an active BotStar account and your appId, the two prerequisites the Make documentation names. A connection is your BotStar account linked to Make once, then reused by every BotStar module you add later.

  2. 02

    Open the connection window

    Add any BotStar module to a scenario and click Create a connection. You can give the connection a name, which helps when you manage several bots or several BotStar accounts from the same Make workspace.

  3. 03

    Authorize and save

    Follow the window: either approve Make on the BotStar page or paste the key BotStar gives you, depending on what the window asks for. Then click Save. The module now shows your connection and is ready to be set up.

First scenario

Your first scenario with BotStar

GoalWhen a user asks for a human in BotStar, Make passes the request to the tool your team works in.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor. This first slot holds the trigger, the module that starts everything.

  2. 02

    Pick the takeover trigger

    Search for BotStar, choose Watch New Request for Human Takeover and click Create a connection, or pick the connection you already made. Fill the fields the module shows.

  3. 03

    Add the destination

    Click the + to the right of the trigger and add a module from the app your team reads: chat, email, helpdesk. Map the data coming from BotStar into its fields.

  4. 04

    Test with Run once

    Click Run once, then ask for a human in your bot. Each item passed between modules is a bundle; open it to check what BotStar actually sent before you trust the mapping.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, BotStar calls Make when the request happens instead of Make checking every 15 minutes, the default rhythm of a scheduled scenario.

Triggers

The BotStar triggers

4 modules start a scenario when something happens in BotStar. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by BotStar as soon as it happens.

BotStar1Watch New Checkpoint Record

Watch New Checkpoint Record

Instant trigger

In Make“Triggers when a new checkpoint record is created.”

This trigger turns a checkpoint reached in your bot into the start of a scenario, so a step you marked in a conversation flow can push its record to another app. Each new record arrives in Make as one bundle you can map.

How it fires
instant, BotStar calls Make through a webhook as soon as the checkpoint record is created.
When to use it
pick it when the moment that matters is a precise point in the flow, such as the end of a quote request, rather than a tag or a subscription.
Watch out
run a real conversation up to the checkpoint during Run once, otherwise Make has no record to show you.
BotStar2Watch New Request for Human Takeover

Watch New Request for Human Takeover

Instant trigger

In Make“Triggers when a user request to contact human operator.”

Here is the trigger that keeps a frustrated user from waiting: it starts your scenario the moment someone in the bot asks to talk to a human operator, so your team can hear about it where they already work.

How it fires
instant, BotStar alerts Make by webhook when the request is made.
When to use it
choose it for support and sales handovers, when a person needs to pick up the conversation quickly.
Watch out
each request uses operations, the unit Make counts on your plan, in every module of the scenario, so keep the alert chain short.
BotStar3Watch New Subscriber

Watch New Subscriber

Instant trigger

In Make“Triggers when a user subscribes to receive broadcast messages.”

You get a copy of every new broadcast subscriber in Make: the trigger starts when a user agrees to receive broadcast messages from your bot, ready to be sent on to a mailing list or a CRM.

How it fires
instant, BotStar notifies Make through a webhook once the user subscribes.
When to use it
use it when your bot is a way to grow an audience and those contacts must also exist outside BotStar.
Watch out
to test it, subscribe with your own account in the bot while Run once is waiting, so a real bundle shows up.
BotStar4Watch New Tag on User

Watch New Tag on User

Instant trigger

In Make“Triggers when a new tag is added to a user.”

Tags become signals with this trigger: whenever a tag is added to a user in BotStar, your scenario runs and can pass that user on, for example to a sales pipeline when the tag marks a qualified lead.

How it fires
instant, BotStar contacts Make via webhook as soon as the tag lands on the user.
When to use it
prefer it over the subscriber trigger when your bot already sorts users with tags, because the tag says why the user matters.
Watch out
the documentation mentions no way to pick a single tag, so expect a run for every new tag and plan what the next modules do with the others.
Need help

Need help automating BotStar with Make?

A person reads every message.

FAQ

BotStar and Make: common questions

01Is the BotStar Make integration free?
Yes, BotStar is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer, with a minimum interval of 15 minutes between scheduled runs. Paid plans lift active scenarios to unlimited, shorten the interval to 1 minute and allow 40 minutes per run. Usage is counted in operations each month. You still need your own active BotStar account, which is billed by BotStar.
02What do you need to connect BotStar to Make?
You need an active BotStar account and your appId, the two prerequisites listed in the Make documentation. In the scenario, add a BotStar module, click Create a connection, optionally give it a name, then authorize Make or paste the key BotStar provides, and click Save. Make does not publish BotStar specific connection steps, so these are the generic ones. The same connection then serves every BotStar module you add. Keep the appId somewhere your team can find it, because every new connection asks for the same details.
03Do the BotStar triggers in Make react in real time?
Yes. All 4 BotStar triggers are instant: BotStar calls Make through a webhook as soon as the event happens, whether that is a checkpoint record, a human takeover request, a new subscriber or a new tag. The scenario does not wait for the 15 minute schedule that applies to scheduled triggers. Make shows a lightning badge on these modules to mark them as instant. In practice, this means your support or sales team hears about a takeover request or a qualified lead while the user is still in the conversation, not long after they have left the bot.
04What if the BotStar module you need is missing in Make?
It depends on what is missing. BotStar in Make offers only 4 triggers and no action, search or Make an API Call module, so you cannot send a message or edit a user from Make. Build the rest of the scenario with other apps, or start from a trigger in another tool. If the gap blocks your project, the Hack'celeration team can look at the options with you through the help form.
05Should you use Make or n8n for BotStar?
It depends on your setup. On the Make side, BotStar gives you 4 instant triggers you can use without code, and the rest of the scenario relies on other apps. If your team already builds automations in n8n, check whether a BotStar node exists there and what it covers before switching tools. Pick the platform where your other apps and your team's habits already are; the comparison page linked above lays out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations