- Home
- Resources
- Integrations
- Landbot
Landbot Zapier integrationAutomate Landbot with Zapier.
The Landbot Zapier integration has 1 trigger, 0 actions and 0 searches. It works in one direction: when a visitor reaches a set point in your chatbot conversation, Zapier hands what they typed to your CRM, your sheet or your inbox, straight away.
Verified Trustpilot reviews · AI, automation & growth agency
What the Landbot Zapier integration actually does
Landbot is a no-code builder for chatbots that greet and question the people visiting your site. The Zapier side has a single job: it notices when a conversation reaches the block you placed for it, and passes the answers collected so far to any other app. It never writes back into the bot.
Three things people get out of it, all resting on Zapier Block Activated:
Leads in the CRM before the chat window closes. Place the Zapier block right after the bot asks for an email, and each new contact reaches your sales tool while the visitor is still on the page.
A live log of every qualified conversation. Send name, company and answers to a spreadsheet row, so marketing can sort by source without exporting anything.
An alert for the hot ones. Put the block only on the branch where the visitor asks for a demo, and the Zap pings your sales channel for that branch alone.
What Zapier does not do here: it cannot start, edit or end a conversation, send a message through the bot, or look up an existing visitor. There are no actions and no searches for Landbot on Zapier. And the Zap only fires at the block you placed: a visitor who drops off before it leaves no trace in the Zap.
If you are weighing platforms, see our n8n vs Zapier comparison. To learn the editor, see our Zapier training page.
Zapier words in one minute
Terms you will see in the editor, each in plain words, once.
- Zap
- The automation you build: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event that starts the Zap. For Landbot, it is a visitor reaching the Zapier block you placed in the conversation.
- Action
- What the Zap does next, in another app here: add a row, create a contact, send a message. Landbot itself offers none.
- Task
- The unit Zapier bills. Each action that completes successfully is one task, counted against the monthly allowance of your plan.
- Instant trigger
- A trigger the app reports itself, the moment the event happens. Landbot works this way, so no timer is involved.
- Polling trigger
- The opposite: Zapier checks the app on a timer whose length depends on your plan. Most apps work like this, Landbot does not.
- Filter
- A step that lets the Zap continue only when the data meets your condition. Adding one makes the Zap multi-step, so paid.
What a Landbot Zap costs you
Short version: the conversation itself costs nothing. You pay for what happens after it.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps only
- TriggerInstant, free, no polling delay
- Each successful action after it1 task
The trigger never consumes a task. Each action that succeeds in the next app does, and a failed one does not. Landbot is not a premium app, so it runs on the free plan: 100 tasks a month, and two-step Zaps only. Because the trigger is instant, the 15-minute check of the free plan does not apply to it. Add a filter, a second action or a search, though, and the Zap becomes multi-step, which needs a paid plan.
Connect your Landbot account
- 01
Open the Apps page
In your Zapier account, open the Apps page and click + Add connection. You need a Landbot account with at least one bot already built, since the trigger asks you to pick one.
- 02
Find Landbot and start the link
Type Landbot in the search box of the dialog, pick it from the results, then click Add connection. A new browser tab opens on the Landbot side to finish the link.
- 03
Sign in and grant access
Log in to Landbot in that tab and let Zapier reach the account. The connection is stored once under Apps, and every Zap that starts from Landbot reuses it from then on.
Your first Landbot Zap, step by step
GoalSend each lead who asks for a demo to a spreadsheet, and skip visitors who left no email.
- 01
Build: place the block, pick the trigger
In Landbot, drop the Zapier Integration block where the lead is complete. In Zapier, create a Zap and pick Zapier Block Activated, then your bot.
- 02
Test with a real conversation
Chat with your own bot until you pass the block, then test the trigger. Zapier brings back the three most recent items, so you map fields on real answers.
- 03
Add the filter
From the plus icon, add Filter: field Email, rule "exists". This keeps empty leads out, and turns the Zap into a multi-step one that needs a paid plan.
- 04
Add the sheet action
Pick Google Sheets and the row action, choose the file, then map name, email and the answers from the bot to the matching columns.
- 05
Test, then publish
Test the action and check the new row. When it looks right, click Publish to switch the Zap on. Conversations from before that moment are not picked up.
The Landbot trigger
1 event starts a Zap when something happens in Landbot, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Zapier Block Activated
Instant triggerIn Zapier“Triggers when a visitor reaches the "Zapier Integration" Block within a Landbot.”
Starts your Zap each time a visitor reaches the Zapier Integration block inside one of your bots, and passes that visitor's data on to the next step. Where you drop the block decides which visitors count.
When a Landbot Zap breaks
Zapier publishes no help article and no specific limit for Landbot. The failures below come from how Zaps behave in general.
Most issues trace back to where the block sits in the bot, to old conversations someone expected to see, or to the app after Landbot. If you are stuck, see our Zapier troubleshooting guide.
Past conversations are never sent
A Zap only reacts to what happens after it is published. Leads collected by the bot last week stay in Landbot; moving them is a separate job.The block sits in the wrong branch
The trigger fires only when a visitor reaches the Zapier block. Put it on one branch only, and every visitor who takes another path is silently skipped.A loop eats your tasks
If the Zap writes somewhere that feeds the bot back into the same block, it sets itself off again and again and burns through the task count fast.A sudden flood is held back
If a campaign sends a huge burst of conversations at once, Zapier's flood protection can hold the batch back before the next app receives it.
Need help automating Landbot with Zapier?
A person reads every message.



