Resources · Make integration

Landbot Make integrationAutomate Landbot with Make.

What happens to a Landbot chat once the bot is done talking? The Landbot Make integration answers with 16 modules: one instant trigger, 13 actions and 2 searches. This guide is for support and sales teams, and it walks you from the connection to a first live scenario.

Try the Landbot integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Landbot Make integration do for you?

The Landbot Make integration links your Landbot account to Make so that chats, customers and tickets move without copy and paste. In Make, you build a scenario: the automation itself, made of modules, where each module is one brick such as a trigger, an action or a search.

Tickets that open themselves. Watch Events wakes the scenario when something happens in Landbot, and Create a Ticket logs the case for your team. Update a Ticket then keeps its status in line as the conversation moves on.

A human when the bot runs out of answers. Assign a Customer to the Agent passes the chat to a person, and Assign A Customer to the Bot sends it back once the question is settled. Send a Text lets the customer know what comes next.

Richer customer profiles. Add a Custom Field and Update a Custom Field write what you learn elsewhere, an order status or a plan name, straight onto the Landbot profile.

Two limits to keep in mind. Watch Events only works on the Landbot PROFESSIONAL and BUSINESS plans, and Make labels its Landbot documentation as AI generated, so check any important detail with Landbot. When a listed module falls short, Make an API Call reaches the rest of the Landbot API. Landbot may also have an n8n node; the n8n vs Make comparison sets out how the two tools differ. For the bigger picture, read our Make review or follow the Make training.

Connect

How do you connect your Landbot account to Make?

  1. 01

    Copy your API token

    In Landbot, click your avatar at the bottom left of the dashboard, pick Account in the menu, and copy the API token shown in the account information section. Make asks for it in the next step.

  2. 02

    Add a Landbot module

    In your Make scenario, add any Landbot module and click Create a connection. A connection is your Landbot account linked to Make once; every Landbot module in your scenarios reuses it.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear label helps when several accounts coexist. Paste the token you copied, or follow the prompts on screen, and save.

First scenario

Your first scenario: turn a Landbot event into a ticket

GoalWhen an event happens in Landbot, Make opens a ticket so the case is tracked.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module.

  2. 02

    Pick Watch Events

    Search for Landbot, choose Watch Events, then click Create a webhook and Create a connection with your API token.

  3. 03

    Add Create a Ticket

    Click the + to the right of the trigger, pick Landbot again, then Create a Ticket. Map data from the event into the ticket fields Make displays.

  4. 04

    Test with Run once

    Click Run once, then trigger an event in Landbot. Open each module to read the bundle it received, a bundle being one item passed from module to module.

  5. 05

    Switch it on

    Once the test ticket looks right, switch the scenario on. From then on Landbot calls Make through the webhook each time an event occurs, with no polling needed.

Triggers

What starts a Landbot scenario

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

Landbot1Watch Events

Watch Events

Instant trigger

In Make“Trigger when a new event occurred. Available only for PROFESSIONAL and BUSINESS plans.”

Your scenario starts the moment something happens in Landbot, so the follow-up work begins while the conversation is still fresh. It is the only trigger this app offers in Make.

How it fires
instant, meaning Landbot calls Make through a webhook as soon as the event happens, shown by the lightning badge on the module.
When to use it
any flow that should react to chat activity, like opening a ticket or updating a record in another tool.
Watch out
Landbot only allows it on its PROFESSIONAL and BUSINESS plans, and the webhook must be created before the connection.
Modules

Every Landbot module, and when to reach for it

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

Landbot1

Add a Custom Field

Action

In Make“Add custom field value to the customer's profile.”

A new piece of information lands on the customer's Landbot profile, so the bot and your agents see it in the next chat. Pick it when the value does not exist on the profile yet.

When to use it
a payment tool confirms an order and you want the order status stored next to the contact.
Watch out
for a value already on the profile, Update a Custom Field is the better fit.
Landbot2

Assign a Customer to the Agent

Action

In Make“Assign a customer to the agent.”

Hands the conversation over to a human agent, so a customer stuck with the bot reaches a person. It is the handoff half of the pair with the bot assignment module.

When to use it
a lead flagged as high value in your CRM should talk to sales, not to a script.
Watch out
plan the way back, or the customer stays with the agent after the issue is closed.
Landbot3

Assign A Customer to the Bot

Action

In Make“Assign a customer to the bot.”

Returns a customer to the bot, freeing your agent's queue once the human part of the exchange is over. Think of it as the closing move after a manual handoff.

When to use it
a ticket is marked solved elsewhere and the bot should take over again for follow-up questions.
Watch out
run it only when the case is really closed, or the customer loses the person helping them mid-conversation.
Landbot4

Create a Ticket

Action

In Make“Creates a ticket.”

Opens a ticket in Landbot, so a request from a chat or from another app becomes a case your team can track until it is solved. Pick it whenever a request needs an owner and a follow-up.

When to use it
Watch Events reports a conversation that needs a follow-up, or a form in another tool asks for help.
Watch out
each bundle that reaches this module opens its own ticket, so a trigger that fires twice for one case leaves you with two tickets.
Landbot5

Get a Channel

Action

In Make“Returns channel information by ID.”

Pulls the details of one Landbot channel from its ID, which tells later modules where a conversation comes from. Useful as a lookup step between the trigger and a routing decision.

When to use it
you route requests differently depending on the channel the customer used.
Watch out
it needs the channel ID; without one from a previous module, it has nothing to fetch.
Landbot6

Get a Customer

Action

In Make“Returns customer's details by ID”

Fetches the full details of one customer from their ID, giving the rest of the scenario the profile to work with. Choose it over List Customers when you already know exactly who you need.

When to use it
an event names a customer and the next module needs their profile data, such as a custom field.
Watch out
no ID, no result; map it from the trigger or a search first.
Landbot7

Get a Ticket

Action

In Make“Returns information about the selected ticket.”

Reads the current state of a single ticket, so your scenario decides on fresh information rather than on what it saw earlier. It pairs naturally with Update a Ticket.

When to use it
before changing a ticket, check where it stands so a later step does not undo a colleague's work.
Watch out
it returns one ticket; to scan several, List Tickets is the right module.
Landbot8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Landbot API through the connection you already set up, which covers whatever the 15 other modules leave out. No second login is needed.

When to use it
a Landbot feature you rely on has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Landbot API reference open and test the result with Run once before relying on it.
Landbot9

Send a Location

Action

In Make“Send a location to the customer.”

Drops a location into the customer's conversation, so they get directions without asking a human for them. It fits businesses where the next step happens somewhere physical.

When to use it
a booking is confirmed in another app and the customer should receive the address of the shop or venue.
Watch out
it sends to one customer per bundle, so a list of customers means one operation each.
Landbot10

Send an Image

Action

In Make“Send an image to the customer.”

Puts a picture in front of the customer inside the chat, which often explains more than a paragraph could. A product shot, a map or a receipt all work.

When to use it
the customer asked about an item and your catalog in another tool holds the matching image.
Watch out
on the Make Free plan, files top out at 5 MB, so large images may fail.
Landbot11

Send a Text

Action

In Make“Send a text to the customer.”

Writes a message to the customer from your scenario, keeping them informed without an agent typing anything. The text can mix fixed wording with data mapped from earlier modules.

When to use it
a ticket changes status and the customer should hear about it in the same conversation.
Watch out
if Watch Events starts the scenario, make sure the message you send cannot itself fire the scenario again.
Landbot12

Update a Custom Field

Action

In Make“Updates a custom field.”

Replaces the value of a custom field that already exists, so the profile reflects today's situation instead of last month's. Pick it rather than Add a Custom Field whenever the field is in place.

When to use it
a subscription changes in your billing tool and the Landbot profile should follow.
Watch out
the old value is overwritten, so read it first with Get a Customer if you need a record of it.
Landbot13

Update a Ticket

Action

In Make“Updates an existing ticket.”

Changes an existing ticket, so its status in Landbot matches what really happened elsewhere. It closes the loop that Create a Ticket opened.

When to use it
a refund is issued in your payment tool and the related ticket should move forward.
Watch out
it acts on one ticket, so you need its ID from a trigger, Get a Ticket or List Tickets.
Landbot14

List Customers

Search

In Make“Lists customers.”

Returns your Landbot customers as separate bundles, one per customer, which lets the next modules process each of them in turn. Reach for it when you do not know the IDs in advance.

When to use it
copying your contacts into a spreadsheet or CRM so both tools share the same list.
Watch out
every returned customer feeds the next modules, and each of those runs counts as an operation on your Make plan.
Landbot15

List Tickets

Search

In Make“Lists tickets.”

Brings back the tickets stored in Landbot, zero, one or many, so you can report on them or act on each. With no trigger available on your plan, it can also start a scheduled scenario.

When to use it
building a view of open cases in a spreadsheet for the support lead.
Watch out
an empty result is normal when nothing matches, and the scenario simply stops there.
Need help

Need help automating Landbot with Make?

A person reads every message.

FAQ

Landbot and Make: common questions

01Is the Landbot Make integration free?
Yes, on the Make side. Landbot is a standard app, available 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 lift these limits, with a 1 minute minimum interval and unlimited active scenarios. On the Landbot side, you need an active account with an API token, and Watch Events is reserved for the Landbot PROFESSIONAL and BUSINESS plans.
02What do you need to connect Landbot to Make?
An active Landbot account and its API token. You find the token by clicking your avatar at the bottom left of the Landbot dashboard, opening Account, and copying it from the account information section. In Make, add a Landbot module, click Create a connection, give it a name if you like, and paste the token. For Watch Events, click Create a webhook before creating the connection, otherwise Landbot has nowhere to send its events.
03Does the Landbot trigger react in real time?
Yes. Watch Events is an instant trigger: Landbot calls Make through a webhook as soon as the event happens, so there is no polling interval to wait for. The catch is the Landbot plan, since this trigger only works on PROFESSIONAL and BUSINESS. Without it, you can start a scenario on a schedule instead, for example with List Tickets as the first module. A new scenario runs every 15 minutes by default, and that is scheduled, not real time.
04What if a Landbot module is missing in Make?
Use Make an API Call. It calls any endpoint of the Landbot API with the connection you already have, which covers whatever the 15 listed actions and searches do not. Keep in mind that Make marks its Landbot documentation as AI generated and possibly inaccurate, so confirm important behavior in the Landbot documentation or with Landbot directly before you build on it. Run once is the safest way to check what a call really returns.
05Should you use Make or n8n for Landbot?
It depends on where the rest of your automations live. On Make, Landbot comes with 16 modules, including an instant trigger, ticket handling and customer messaging, and anything else goes through Make an API Call. Landbot may also be available as an n8n node, so compare the two on the modules you actually need and on the tool your team already knows. Running every scenario in one place keeps connections and troubleshooting simpler.
Same platform

Other docs you might need on this stack.

Browse all integrations