Landbot
CommunicationConnect AI agents to Landbot chatbots on WhatsApp and web. Agents enrich customer profiles with CRM data, send proactive WhatsApp templates, route conversations to bots or human agents, and sync captured leads into downstream systems.
What This Integration Enables
A chatbot is a data collection instrument attached to a routing problem. The bot's conversation gathers what a lead form never could, and then everything depends on what happens next: does the profile reach the CRM, does the hot lead reach a person while the conversation is still warm, does the follow-up reach the customer inside WhatsApp's rules? Landbot handles the conversation; FlowRunner handles the everything-next. Agents move profiles, enrich fields, pick the right lane between bot and human, and send proactive templates when the 24-hour window will not stretch. - Enrich customer profiles with CRM and database context, merged onto existing fields with Set Customer Fields - Send proactive WhatsApp templates for reminders and order updates outside the 24-hour service window - Look up customers by phone, email, or name, and reply through their connected channel - Escalate conversations to a live agent's inbox, or launch customers into a specific bot at a chosen block - Sync bot-captured leads into spreadsheets, CRMs, and team channels as they arrive The routing actions are the interesting part: they make the bot-versus-human decision a programmable step, which is exactly where a [human-in-the-loop](/concepts/human-in-the-loop) discipline belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The lead loop that runs both directions
Find Customer By Field resolves a bot lead by phone number, and the agent syncs the profile into [HubSpot](/integrations/hubspot), creating or updating the contact. When the CRM assigns a lifecycle stage, Set Customer Fields writes it back onto the Landbot customer, so the next conversation the bot has with this person starts from what sales already knows. Two systems, one profile, no exports.
High-value leads meet a person, fast
When the bot captures a lead, Get Customer pulls the profile and the row logs to [Google Sheets](/integrations/google-sheets). Leads that clear the value bar do not go into a queue: Assign Customer To Agent drops the live conversation into the right salesperson's inbox for takeover while the prospect is still typing. After resolution, Unassign Customer releases the thread and the summary posts to [Slack](/integrations/slack), so the team has a record of every handoff.
Reminders that respect the window
The appointment flow checks the calendar the day before and sends each customer their reminder. Inside the 24-hour service window, Send Message delivers it conversationally. Outside the window, the agent selects the approved reminder template from List WhatsApp Templates, fills the placeholders, and calls Send Template. No-shows drop; the WhatsApp number's standing does not, because every message went out in the lane the platform allows.
Human-in-Loop Highlight
Send Template is proactive outreach into WhatsApp, the most personal inbox a customer has, and at batch scale it is the costliest send in this connector. A template blast to the wrong segment, the wrong language variant from List WhatsApp Templates, or placeholders filled with another customer's data goes out under your business number to people who did not start the conversation, and recipients who resent it can report the number they resent. So FlowRunner treats single transactional templates and batch campaigns differently. The reminder tied to one customer's appointment fires autonomously. A batch send stops first: the owner sees the exact template, the filled parameters for a sample of recipients, and the size of the opted-in audience from List Customers. Approval releases the batch. The agent handles the mechanics of a thousand sends; a person answers for whether those thousand people should hear from you today.
Agent Capabilities
13 actionsCustomers
4- List Customers Retrieves the customers who have interacted with your bots, filterable by opt-in status, with cursor pagination. Each record carries contact details, assigned bot, and custom fields.
- Get Customer Retrieves one customer's full profile by ID: name, contact details, channel, assigned bot and agent, and every custom field the conversations collected.
- Find Customer By Field Searches customers by phone, email, or name, optionally restricted to opted-in customers. The resolution step before any message or sync.
- Set Customer Fields Sets or updates custom fields on a profile, merged into existing data. The write that carries CRM context back into the conversation layer.
Messaging
3- Send Message Sends text and media messages to a customer through their connected channel via an API-chat bot, delivered in order. Inside WhatsApp's 24-hour window only; beyond it, templates take over.
- Send Template Sends a pre-approved WhatsApp template with header, body, and button parameters, required for initiating conversations outside the 24-hour window. Batch sends run behind this page's human gate.
- List WhatsApp Templates Retrieves the account's WhatsApp templates with ID, language, category, and approval status. The check that keeps flows sending only what is approved.
Routing
3- Assign Customer To Agent Places a customer's conversation in a specific human agent's inbox for live takeover. The escalation step for leads worth a person's time.
- Assign Customer To Bot Assigns or launches a customer into a specific bot, optionally starting at a chosen block. The routing step for automated paths.
- Unassign Customer Releases a customer from their current agent or bot after resolution, keeping inboxes clean and handoffs recorded.
Account
3- List Bots Retrieves the account's bots with ID, name, and channel type, for routing decisions.
- Get Bot Retrieves one bot's configuration, for confirming settings before customers route into it.
- List Agents Retrieves the human agents with IDs, names, and emails. The lookup behind every live-takeover assignment.
Frequently Asked Questions
What can FlowRunner do with Landbot?
FlowRunner agents can run List Customers, Get Customer, and Find Customer By Field in Landbot, plus 10 more actions.
Does connecting Landbot to FlowRunner require OAuth?
No. Landbot connects to FlowRunner with an API key, no OAuth flow required.
Can Landbot trigger a FlowRunner workflow automatically?
Landbot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Landbot
$100 in credits. No card required. Connect in minutes.