Resources · Make integration

Botcake Make integrationAutomate Botcake with Make.

Want your Botcake chatbot to speak up when something happens in another tool? The Botcake Make integration gives you 2 action modules: one sends a flow, the other calls the Botcake API. This page shows ops and marketing builders how to connect the account and ship a first working scenario.

Try the Botcake integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Botcake Make integration do for you?

The Botcake Make integration lets another app tell your Botcake chatbot what to do next. In Make, you build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as an action. Botcake brings 2 action bricks, so it usually sits at the end of the chain, reacting to something that happened elsewhere.

Welcome a new lead on Messenger or WhatsApp. A form tool catches a signup, and the Send a Flow module pushes the matching Botcake flow to that contact. The conversation starts from your chatbot, not from a manual copy and paste. The 123FormBuilder Make integration is one way to catch that signup.

Hand a paying customer to the right sequence. When an order or a booking lands in another tool, Send a Flow can open the onboarding flow you already designed in Botcake, so every buyer gets the same first steps.

Reach Botcake features that have no module. The Make API Call module sends an authorized request to Botcake with your existing connection. It suits builders who know which Botcake API endpoint they need.

Know the limits before you plan. Botcake has no trigger in Make, so a Botcake event cannot start a scenario by itself. Make also says its documentation for this app is limited, because little public information exists about Botcake. If you want an outside opinion on the platform first, read our Make review. Botcake may also have a node in n8n; the n8n vs Make comparison lays out both tools side by side.

Connect

How do you connect your Botcake account to Make?

  1. 01

    Add a Botcake module

    In your scenario, click the +, search for Botcake and pick Send a Flow. Then click Create a connection. A connection is your Botcake account linked to Make once, then reused by both Botcake modules.

  2. 02

    Name the connection

    This step is optional, but a clear name helps later. If you run several Botcake accounts, for instance one per client, label each connection after its account, so you pick the right one in every module.

  3. 03

    Authorize and save

    Depending on what Make shows, either approve access on the Botcake page that opens or paste the key Botcake gives you. Then click Save, and the connection appears in the module.

First scenario

Build your first scenario with Botcake

GoalWhen a new lead reaches another app, Make sends that person a Botcake flow.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since Botcake has no trigger, the first module comes from the app where your leads arrive, such as a form tool.

  2. 02

    Set the starting module

    Search that other app, pick its module that watches new entries and create its connection. Fill its fields; Make lists the forms or sheets it can read once the connection exists.

  3. 03

    Add Send a Flow

    Click the + on the right of the first module, search Botcake and choose Send a Flow. Select your Botcake connection, or create it as shown above.

  4. 04

    Map the lead data

    Fill the Botcake fields Make displays, dragging in data from the first module. Each bundle, meaning one item passing between modules, here one lead, gets its own flow.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check that Botcake sent the flow.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Every module run counts as one operation, the unit Make bills on your plan.

Modules

What the Botcake modules do

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

Botcake1

Make API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you send your own authorized request to Botcake, reusing the connection you already created. Think of it as a spare key for what Send a Flow does not cover.

When to use it
pick it when the action you need is not covered by Send a Flow and you know the Botcake API endpoint to call.
Watch out
Make documents Botcake only partially, so you will need Botcake's own API reference to shape the request.
Botcake2

Send a Flow

Action

In Make“Sends a flow from Botcake.”

Send a Flow gets a flow you designed in Botcake moving from Make, so a contact receives that chatbot sequence without anyone opening Botcake.

When to use it
choose it at the end of a scenario, right after another app reports a new lead, order or booking that deserves a message.
Watch out
build and test the flow in Botcake first; the module sends a flow that already exists in Botcake, so fix the wording there.
Need help

Need help automating Botcake with Make?

A person reads every message.

FAQ

Botcake and Make: common questions

01Is the Botcake Make integration free?
Yes, Botcake is a standard app, so you can use it on the Make Free plan. That plan gives you 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) bring the interval down to 1 minute, remove the active scenario cap and count usage in credits each month.
02What do you need to connect Botcake to Make?
A Botcake account and a Make account are enough to start, since the documentation lists no other prerequisite. You add a Botcake module, click Create a connection, optionally name it, then either authorize Make on the Botcake page or paste the key Botcake provides, and save. Make notes that its Botcake documentation is limited, so follow the fields shown on screen during setup. Once saved, the same connection serves both Botcake modules, so you only do this once per account.
03Can a Botcake event start a Make scenario in real time?
No, not by itself, because Botcake has no trigger module in Make. The scenario has to start elsewhere: either with an instant trigger from another app, which that app calls through a webhook as soon as something happens, or with a schedule on the first module, which runs every 15 minutes by default. Botcake then acts at the end of the chain through Send a Flow or Make API Call.
04What if the Botcake module you need is missing in Make?
It depends on what you need. Botcake offers 2 modules only, and Make states its documentation for this app is limited. Make API Call covers some gaps if you know the Botcake API, but that is the only generic request tool here. Otherwise, route the data through another app in your scenario, or ask the team for help designing the workaround. The Make troubleshooting resources and the Make training can also help you read the errors a request returns.
05Should you use Make or n8n for Botcake?
It depends on where the rest of your automations live. Many apps also have an n8n node, so check whether Botcake has one before you compare. In Make you get the 2 modules described on this page, a visual editor and the Free plan to test. The honest criterion is simple: pick the tool your team already runs, so that Botcake flows sit next to the scenarios that feed them.
Same platform

Other docs you might need on this stack.

Browse all integrations