Resources · Make integration

Botsify Make integrationAutomate Botsify with Make.

What happens to the leads your chatbot collects once the chat ends? The Botsify Make integration gives you 4 triggers and 3 actions to pass them on. This page is for teams running a Botsify bot, and it walks you from connection to a working first scenario.

Try the Botsify integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Botsify Make integration do for you?

The Botsify Make integration links your chatbot to a Make scenario, which is the automation you build in Make as a chain of modules. Each module is one brick: a trigger that watches Botsify, or an action that writes back to it. When your bot collects a lead, a form or a request for help, Make can pick it up and act on it.

Never miss a visitor who asks for a person. Botsify Human Help starts a scenario when someone chatting with your bot needs human help, so a support lead can be alerted in the tool the team already watches.

Turn every chat lead into a follow-up. Watch New Leads catches the leads your website bot collects, and Send Message to User can then reply to that user inside the chat. For an online training company, that means a prospect gets a next step without anyone typing it.

Keep your bot's user profiles current. Watch Form Submissions or Watch New Subscribers from Facebook feed Add / Update User Attribute, so what a user tells one channel shapes the next conversation. Create Story adds a new story to the bot when you need one built from outside data.

What the integration does not do: all 4 triggers are scheduled, so Make checks Botsify on the scenario's schedule rather than hearing from it instantly, and there is no universal API call module to reach endpoints the 7 modules skip. The Botsify documentation on Make is also flagged as AI-generated, so check important details with Botsify. Before you commit, the Make review gives you the full picture of the tool, Make pricing helps you pick a plan, and n8n vs Make compares both tools if you still hesitate.

Connect

How do you connect Botsify to Make?

  1. 01

    Create an API key in Botsify

    In the Bot Dashboard, open Settings from the left sidebar, choose API keys, then click Create an API Key. Give the key a name, click Create and copy the key shown in the window.

  2. 02

    Add a Botsify module in Make

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

  3. 03

    Paste the key and save

    Type a label in Connection name if you run several bots, it is optional. Paste the API key you copied from Botsify, confirm, and Make can now read your bot's leads and users.

First scenario

Your first scenario: reply to every new chatbot lead

GoalWhen your website bot collects a new lead in Botsify, Make sends that user a follow-up message in the chat.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module, the one that starts everything.

  2. 02

    Pick the lead trigger

    Search for Botsify, choose Watch New Leads and select the connection you created. If none exists yet, click Create a connection and paste your API key.

  3. 03

    Add the reply

    Click the + to the right of the trigger and add Send Message to User. Map the user from the lead bundle, a bundle being one item passed between modules, then write your text.

  4. 04

    Test with Run once

    Leave a test lead through your website bot, then click Run once. Open the bubbles on each module to read the bundle it received and check that the message reached the chat.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default and never shorter than that on the Free plan, then turn the scenario on. Each module run counts as one operation on your plan.

Triggers

Which Botsify events can start a scenario?

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

Botsify1Botsify Human Help

Botsify Human Help

Scheduled trigger

In Make“Triggers when a person talking to Bot needs Human Help”

This trigger tells you when a person talking to your bot asks for human help, so the conversation does not stall while the bot keeps guessing. You can route that moment to whoever handles support.

How it fires
scheduled, Make checks Botsify on the scenario's schedule, so the alert arrives at the next check rather than the second it happens.
When to use it
your bot handles common questions but a visitor needs a real answer about an order or a quote.
Watch out
on the Free plan checks run 15 minutes apart at best, so tell users a person will reply shortly rather than immediately.
Botsify2Watch Form Submissions

Watch Form Submissions

Scheduled trigger

In Make“Triggers when a user submits form.”

Each form a user completes inside your Botsify bot becomes a bundle Make can work with, ready to be stored, forwarded or used to update that user. It saves you from exporting answers by hand.

How it fires
scheduled, Make checks Botsify on the scenario's schedule and collects the submissions made since the last check.
When to use it
your bot runs a booking or registration form and the answers must land in another tool.
Watch out
several forms can arrive in one check, and every bundle then runs through the next modules, each run counting as an operation.
Botsify3Watch New Leads

Watch New Leads

Scheduled trigger

In Make“Triggers when any website bot collects a lead from a user.”

Pick this one to start a scenario whenever any of your website bots collects a lead from a visitor. It is the entry point for most sales follow-ups built on Botsify.

How it fires
scheduled, Make checks Botsify on the scenario's schedule and brings in the leads gathered since its previous look.
When to use it
a visitor leaves contact details to receive a brochure and you want the sales team to see the lead without opening Botsify.
Watch out
each lead is a separate bundle, so several leads found in one check run the next modules several times, each run counting as an operation.
Botsify4Watch New Subscribers from Facebook

Watch New Subscribers from Facebook

Scheduled trigger

In Make“Triggers when a new user starts talking to your Facebook bot.”

Your Facebook bot gains a new contact, and this trigger hands that person to Make the moment it next checks. It keeps your Messenger audience in sync with the rest of your tools.

How it fires
scheduled, Make checks Botsify on the scenario's schedule, not through an instant webhook.
When to use it
you run ads that open a conversation with your Facebook bot and want each new subscriber welcomed or recorded.
Watch out
it concerns your Facebook bot only; for visitors of your website bot, Watch New Leads is the trigger to pick.
Modules

What can Make do in Botsify?

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

Botsify1

Add / Update User Attribute

Action

In Make“Creates or updates bot users' attributes.”

Store what you learn about a chat user on their Botsify profile, creating the attribute if it is new or overwriting it if it exists. Your bot can then speak to that user with context.

When to use it
a form answer or a purchase in another app should change how the bot greets that person next time.
Watch out
updating an attribute changes what the bot knows about that user, so map the right user from the trigger before you run it on real contacts.
Botsify2

Create Story

Action

In Make“Creates a new story.”

Create Story adds a new story to your Botsify bot straight from a scenario. It lets content prepared in another tool reach the bot without you rebuilding it by hand in the dashboard.

When to use it
your team drafts answers in a shared sheet and wants each approved entry turned into a story.
Watch out
every run creates a new story, so test with Run once on a single bundle to avoid duplicates.
Botsify3

Send Message to User

Action

In Make“Sends message to a chat user”

Reach a chat user again with a message sent by Make, so your follow-up lands in the conversation they already have with your bot. No need to wait for them to come back and type.

When to use it
right after Watch New Leads, to confirm a request or share the next step.
Watch out
the message goes to the user you map, so check on a test contact first; a wrong mapping sends your text to the wrong person.
Need help

Need help automating Botsify with Make?

A person reads every message.

FAQ

Botsify and Make: common questions

01Is the Botsify Make integration free?
Yes, on the Make side. Botsify is a standard app, so its 7 modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and count usage in credits each month. You still need your own active Botsify account, whose subscription is set by Botsify, not Make.
02What do you need to connect Botsify to Make?
An active Botsify account and an API key. In the Bot Dashboard, go to Settings, then API keys, click Create an API Key, name it, click Create and copy the key. In Make, add a Botsify module, click Create a connection, optionally fill Connection name, then paste the key. The connection is saved once and every Botsify module in your scenarios reuses it, so you do this step a single time per account.
03Does the Botsify trigger react in real time?
No. All 4 Botsify triggers are scheduled: Make checks Botsify on the scenario's schedule instead of receiving an instant webhook. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. For a human help request, that delay matters, so tell users a person will answer shortly and pick the shortest interval your plan allows.
04What if a Botsify module is missing in Make?
It depends on what you need. Botsify has 7 modules in Make and no universal API call module, so you cannot reach other parts of the Botsify API from inside this app. Check first whether another app in Make can take the step instead, for example the tool where your leads end up. If the gap blocks your project, the team can study the case with you through the help form on this page.
05Make or n8n for Botsify?
It depends on your criteria rather than on a winner. This page covers Make, where Botsify offers 4 scheduled triggers and 3 actions, available on every plan. The same app often has an n8n node, so compare the modules you need on each side before choosing. Look at which events you must catch, which actions you must run and which tool your team already knows. The comparison page linked above goes through the criteria for both tools.
Same platform

Other docs you might need on this stack.

Browse all integrations