Integration

Landbot integration

Landbot is a no-code chatbot builder for web, WhatsApp and Messenger. Through its Platform API you can list channels and customers, read a customer's full conversation transcript, send text, images, locations and WhatsApp templates, archive, block and assign customers to agents or bots, read and write customer fields, and register message hooks that post every message of a channel to your URL. Building or editing bots (the alpha Bots API), the AI Agents and Channels design APIs, and APIchat (which takes a separate channel token on another host) are not exposed. Authentication is the agent token from Settings, Account, sent in the Authorization header as Token followed by the token; every call acts as that agent, with its role's permissions.

Connect Landbot How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Landbot.Built from the 29 Landbot tools below, on the connection you add once.

What you can do with Landbot

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Customer, 11 operations

archive_customerArchive customerPUTArchives a customer (list_customers with archived=true returns them). Undo with unarchive_customer.
assign_customer_to_agentAssign customer to agentPUTAssigns the customer's conversation to another agent of the workspace, by numeric agent id.
assign_customer_to_botAssign customer to botPUTMay send messages to the customer: hands the customer to a bot, and with launch=true the bot starts at once (from node, else its start node) and messages the customer; with launch=false it waits for the customer's next message.
assign_customer_to_meAssign customer to mePUTAssigns the customer's conversation to the agent who owns the API token.
block_customerBlock customerPUTBlocks a customer: messages can no longer be sent to them (a send then fails with 412, The customer is blocked). Undo with unblock_customer.
delete_customerDelete customerDELETEDeletes a customer. Returns no body. To keep the customer but take them out of the active list, use archive_customer instead.
get_customerGet customerGETReturns one customer: name, channel, avatar, last message time, unread flag, archive state, assigned agent, registration date, custom fields (a map of field name to value object) and meta data.
list_customersList customersGETLists customers (people who chatted with a bot) with id, name, channel, assigned agent, archive state and custom fields. Filter by channel, agent, archive or opt-in state, or search by name, email or phone prefix.
unarchive_customerUnarchive customerPUTUnarchives a customer, the reverse of archive_customer.
unassign_customerUnassign customerPUTRemoves the assigned agent from the customer's conversation.
unblock_customerUnblock customerPUTUnblocks a customer so messages can be sent to them again.

Message hook, 5 operations

create_message_hookCreate message hookPOSTRegisters a message hook: Landbot then POSTs every message of the channel (customer, bot, agent, system) to url, one per request. Needs a plan with message hooks (else 402).
delete_message_hookDelete message hookDELETEDeletes a message hook from a channel; Landbot stops posting that channel's messages to its url. Returns no body.
get_message_hookGet message hookGETReturns one message hook of a channel: id, name, url, channel_id and timestamps. The token it sends is not returned here.
list_message_hooksList message hooksGETLists the message hooks registered on a channel: id, name, url and timestamps. The token each hook sends is not returned here.
update_message_hookUpdate message hookPATCHChanges a message hook's name, url or token. Fields you leave out keep their current value. Needs a plan with message hooks (else 402).

Customer field, 4 operations

create_customer_fieldCreate customer fieldPOSTCreates a field on a customer. It never overwrites: an existing field fails with 412 (use update_customer_field). To set a field whether or not it exists, create first and update on 412.
delete_customer_fieldDelete customer fieldDELETEDeletes a field (variable) from a customer. Returns no body.
get_customer_fieldGet customer fieldGETReturns one field (variable) of a customer: its name, type, extra metadata and value.
update_customer_fieldUpdate customer fieldPUTChanges the value of an existing customer field. It never creates one: a field that does not exist answers 404 (use create_customer_field). Send type and value together.

Message, 4 operations

list_customer_messagesList customer messagesGETReturns a customer's complete conversation transcript in one call (no pagination). Order is not guaranteed: sort by message_datetime, a YYYY-MM-DD HH:MM:SS string. Fields depend on each message's type.
send_image_messageSend image messagePOSTSends an image to a customer on their channel, from a public URL, with an optional caption. A blocked customer or inactive channel fails with 412.
send_location_messageSend location messagePOSTSends a map location (latitude and longitude) to a customer on their channel. A blocked customer or inactive channel fails with 412.
send_text_messageSend text messagePOSTSends a text message to a customer as the token's agent (an unassigned customer is assigned to that agent). On WhatsApp it arrives only within 24 h of the customer's last message, else use send_whatsapp_template. Blocked or inactive: 412.

Channel, 2 operations

get_channelGet channelGETReturns one channel: id, name, type, active flag, creation time and its web widget colours and images. Type-specific keys (such as facebook_id) may also appear.
list_channelsList channelsGETLists the channels of the workspace (web, WhatsApp, Messenger, APIchat), with id, name, type and active flag. Paginate with offset and limit; total gives the filtered count.

Whatsapp template, 2 operations

list_whatsapp_templatesList whatsapp templatesGETLists the approved WhatsApp templates send_whatsapp_template can send, with id, text and params_number (how many placeholders the body expects). With several or migrated channels, filter by channel_id to avoid duplicates.
send_whatsapp_templateSend whatsapp templatePOSTSends an approved WhatsApp template to a WhatsApp customer. Get template_id and the placeholder count from list_whatsapp_templates. A blocked customer or inactive channel fails with 412.

Whatsapp opt in, 1 operation

opt_out_customerOpt out customerDELETEDeletes the WhatsApp opt-ins recorded for a customer (list_customers filters on them with opt_in). Returns no body.

Use Landbot from Claude Code, Cursor or Codex

Connect Landbot in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Landbot operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Landbot

Create your workspace
Sign up free. Nothing to install.
Connect Landbot once
Add your Landbot connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.