Resources · Make integration

Typebot Make integrationAutomate Typebot with Make.

What happens to a chat once a visitor starts it in your typebot? The Typebot Make integration gives you 6 modules, including an instant trigger, to pass each conversation to your other tools. This page shows how to link your account and build a first scenario.

Try the Typebot integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Typebot Make integration let you automate?

The Typebot Make integration links your Typebot account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick of that chain. With Typebot you get 2 triggers, 2 actions and 2 searches.

Leads that land in your CRM on their own. Watch New Chat starts the scenario as soon as a visitor opens a chat in the typebot you pick. Add the module of another app after it, and the conversation lands where your sales team already works.

A clean map of the answers before you build. Get a Chatbot Chat Form returns an example of the response format, so you can see which data a chat carries and map it field by field in the next module.

An inventory of your bots. List Typebots and List Webhook Blocks are searches: each one can return zero, one or several items, handy when you manage many bots and want to see what exists before wiring anything.

What the integration does not cover: anything outside those 6 modules. For another endpoint of the Typebot API, Make an API Call reuses your connection. If a run fails, the Make troubleshooting guide lists the usual causes. Still weighing tools? Read n8n vs Make, and to get your team up to speed, see our Make training.

Connect

How do you connect your Typebot account to Make?

  1. 01

    Create an API token in Typebot

    In your Typebot dashboard, open Settings and Members, then My account. Under API tokens, click Create, give the token a name, click Create token and copy the value shown in the window.

  2. 02

    Add a Typebot module in Make

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

  3. 03

    Paste the token and save

    The Connection name field is optional; a clear name helps if you link more than one Typebot account. Paste the API token you copied, confirm, and Make now reads your bots in the module fields.

First scenario

Your first scenario with Typebot

GoalWhen a visitor starts a chat in your typebot, Make catches it and reads the format of the answers so you can pass them to another app.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to add the first module.

  2. 02

    Pick Watch New Chat

    Search for Typebot, choose Watch New Chat, click Create a webhook, then Create a connection with your API token. Select the typebot to watch in the list Make shows you.

  3. 03

    Add Get a Chatbot Chat Form

    Click the + on the right of the trigger and add Get a Chatbot Chat Form. Fill its fields with data mapped from the previous module, so you see the shape of the answers.

  4. 04

    Test with Run once

    Click Run once, then open a chat on your bot. Each module shows the bundles it received: a bundle is one item passed from a module to the next, here one chat.

  5. 05

    Switch it on

    Once the bundles look right, add the module of the app that should receive the chat, then switch the scenario on. Every new chat now follows the same path.

Triggers

What can start a Typebot scenario?

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

Typebot1Watch New Chat

Watch New Chat

Instant trigger

In Make“Triggers when a new chat is started in the specified typebot.”

This trigger gives you each new conversation the moment a visitor starts it in the typebot you select, so the rest of the scenario can act while the lead is still warm.

How it fires
instant. Typebot calls Make through a webhook as soon as the chat starts, which is why Make asks you to create a webhook when you add it.
When to use it
a lead capture bot on your pricing page, where sales want each new conversation in their pipeline without refreshing anything.
Watch out
each new chat is one bundle, so every module placed after the trigger uses one operation per chat.
Typebot2Watch Make.com Block Trigger

Watch Make.com Block Trigger

triggerIn the docs only

This trigger is listed in the Make documentation without a description. Its name points to a Make.com block inside your typebot, but nothing official says what it returns, so treat it as something to test before you build around it.

How it fires
scheduled, a type deduced from its listing since the documentation does not describe it. Make checks Typebot on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
when Watch New Chat does not fit your flow and you want to see what this block sends.
Watch out
click Run once first and read the bundles before you rely on them.
Modules

What else can Make do with Typebot?

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

Typebot1

Get a Chatbot Chat Form

Action

In Make“Gets an example of the result of the response format.”

Here you get a sample of how a typebot formats its answers, which shows you which data you can map into the next app instead of guessing.

When to use it
right after Watch New Chat, while you design the scenario and wonder which answer goes into which CRM field.
Watch out
it returns an example of the format, not a list of every chat, so it is a design aid more than an export.
Typebot2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you reach any endpoint of the Typebot API with the connection you already set up, so a missing module never blocks you.

When to use it
when the other five modules do not cover what you need and the Typebot API documentation describes the request.
Watch out
you write the request yourself, so check the endpoint and its parameters in the Typebot documentation before running it.
Typebot3

List Typebots

SearchIn the docs only

Going by its name (the documentation gives no description), List Typebots returns the bots of your account as separate bundles, giving you a quick inventory without opening the Typebot dashboard.

When to use it
an agency or a team running many bots that wants a record of each one in a sheet or a database.
Watch out
it is a search, so it can return zero, one or several bundles, and every module placed after it runs once per bot.
Typebot4

List Webhook Blocks

SearchIn the docs only

This search lists the webhook blocks it finds, which helps you check which parts of your bots already talk to an outside tool before you add another one.

When to use it
during an audit of your flows, when you want to see where data leaves Typebot.
Watch out
the documentation gives no description of this module, so read its output with Run once, and expect zero, one or several bundles.
Need help

Need help automating Typebot with Make?

A person reads every message.

FAQ

Typebot and Make: frequent questions

01Is the Typebot Make integration free?
Yes, Typebot is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, at least 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) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts usage in operations: one execution of one module on one bundle. Your Typebot subscription is a separate matter, handled on the Typebot side.
02What do you need to connect Typebot to Make?
You need an active Typebot account and an API token. Create the token in your Typebot dashboard under Settings and Members, then your account page, in the API tokens section: click Create, name it, click Create token and copy it. In Make, add a Typebot module, click Create a connection, optionally name it and paste the token. For Watch New Chat, which is an instant module, click Create a webhook first, then Create a connection.
03Does the Typebot trigger in Make fire in real time?
It depends on the trigger. Watch New Chat is instant: Typebot calls Make through a webhook as soon as a visitor starts a chat, so the scenario runs right away. Watch Make.com Block Trigger is listed as scheduled (the documentation gives no detail): Make checks Typebot on the scenario's schedule, every 15 minutes by default, never more often than every 15 minutes on the Free plan and down to every minute on a paid plan. Pick Watch New Chat whenever speed matters for a lead.
04What if a Typebot module is missing in Make?
Use Make an API Call. It sends any request to the Typebot API with the connection you already have, so you can reach an endpoint that the other five modules do not cover. You write the request yourself, following the Typebot API documentation. Keep in mind that the Make documentation for this app is marked as AI-generated from the Typebot documentation and may contain mistakes, so test each module with Run once before switching a scenario on.
05Make or n8n for Typebot?
It depends on what you compare. On the Make side, the facts are clear: 6 Typebot modules, including an instant trigger for new chats, a free entry plan with 2 active scenarios, and Make an API Call to cover the rest of the API. Before choosing, check whether n8n offers a Typebot node that covers the same events, then compare the two lists of modules against the scenario you have in mind. The tool that already handles your trigger and your destination app is the one to start with.
Same platform

Other docs you might need on this stack.

Browse all integrations