Integration

Botmaker integration

Botmaker is a conversational AI and customer messaging platform (WhatsApp, Messenger, Instagram, Telegram, webchat, email and more). With this API an agent sends messages and WhatsApp template notifications for real, runs bot intents in chats, reads and updates chats, contacts, messages, sessions, calls and tickets, manages WhatsApp templates, notification campaigns and the blacklist, product catalogs (products, categories, stores, zones), bot entities, variables, typifications, queues and knowledge bases, and reads billing consumption. Left out on purpose: agents and roles, audit logs and agent dashboards, webhooks and their redirection rules, bot constants, API credential routes, private media links, call creation (it returns join links), external catalog platform connections and WhatsApp line registration. Media links, shared locations, recording links, contact addresses, birthdays and pictures, channel tokens and billing contacts are not returned. Message, session, notification result and billed conversation reads add to the account's BI data source costs, and each route has its own rate limit (from one request per minute to hundreds per second). Most lists return only their first page here. Authentication is the API access token from the Botmaker API integration page, sent in the access-token header.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Botmaker

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.

Product, 5 operations

  • delete_productDelete productDELETEDeletes one product from a catalog for real.
  • delete_productsDelete productsPOSTDeletes several products of a catalog by SKU for real.
  • get_productGet productGETReturns one product of a catalog by its SKU.
  • list_productsList productsGETLists or searches a catalog's products (sku, title, price, availability, categories), optionally by category. First page only.
  • upsert_productsUpsert productsPOSTCreates or updates products of a catalog for real, matched by SKU. A new product needs every required field; an update needs only the SKU and the changed fields.

Zone, 5 operations

  • delete_zoneDelete zoneDELETEDeletes one zone from a catalog for real, with its price schema when no other zone uses it.
  • delete_zonesDelete zonesPOSTDeletes several zones of a catalog by code for real, with any price schema left with no zone.
  • get_zoneGet zoneGETReturns one zone of a catalog with its radius, coordinates and attached stores.
  • list_zonesList zonesGETLists a catalog's zones (geographic areas with their own prices) with their stores and coordinates. First page only.
  • upsert_zonesUpsert zonesPOSTCreates or updates zones of a catalog for real, matched by code.

Chat, 4 operations

  • get_chatGet chatGETReturns one chat's state: contact name, email, country, tags, variables, queue, assigned agent and WhatsApp window close time.
  • list_chatsList chatsGETLists chats (contact name, email, tags, variables, queue, agent), latest activity first, up to 250; search by contact id, name or email. First page only: narrow from and to for more.
  • send_read_typing_feedbackSend read typing feedbackPOSTMarks the contact's previous messages as read, or shows them a typing indicator, for real.
  • update_chatUpdate chatPATCHChanges a chat's contact data, tags or variables for real. Send only the fields to change; leave the others out to keep them.

Intent, 4 operations

  • batch_trigger_intentBatch trigger intentPOSTRuns bot intents in up to 500 chats at once for real, typically to send WhatsApp templates; every contact receives what its intent sends and WhatsApp may bill each conversation.
  • get_intentGet intentGETReturns one intent with its bot, topics, triggers and active flag.
  • list_intentsList intentsGETLists the bot's intents with their id, name, bot, topics and triggers. Intent ids and names are what trigger_intent and send_notification take. First page only.
  • trigger_intentTrigger intentPOSTRuns a bot intent in one chat for real, typically to send a WhatsApp template that opens a conversation (billed by WhatsApp, see list_billed_conversations). The contact receives what the intent sends.

Store, 4 operations

  • delete_storeDelete storeDELETEDeletes one store from a catalog for real.
  • delete_storesDelete storesPOSTDeletes several stores of a catalog by code for real.
  • list_storesList storesGETLists a catalog's stores with their code, address and per-SKU availability.
  • upsert_storesUpsert storesPOSTCreates or updates stores and their inventory for real, matched by store code.

Whatsapp template, 4 operations

  • create_whatsapp_templateCreate whatsapp templatePOSTCreates a WhatsApp template and submits it to WhatsApp for approval, for real. Sends nothing to contacts.
  • delete_whatsapp_templateDelete whatsapp templateDELETEDeletes a WhatsApp template for real; it can no longer be sent.
  • get_whatsapp_templateGet whatsapp templateGETReturns one WhatsApp template with its state, category, locale, header, body, footer and buttons.
  • list_whatsapp_templatesList whatsapp templatesGETLists WhatsApp message templates with their state, category, locale and content.

Blacklisted contact, 3 operations

  • add_blacklisted_contactsAdd blacklisted contactsPOSTAdds up to 1000 numbers to the notifications blacklist for real; they stop receiving notifications.
  • list_blacklisted_contactsList blacklisted contactsGETLists the numbers on the notifications blacklist (contacts that never receive notifications). First page only.
  • remove_blacklisted_contactRemove blacklisted contactDELETERemoves one number from the notifications blacklist for real; it can receive notifications again.

Category, 3 operations

  • delete_categoryDelete categoryDELETEDeletes one category from a catalog for real.
  • list_categoriesList categoriesGETLists a catalog's product categories (code, title, parent).
  • upsert_categoriesUpsert categoriesPOSTCreates or updates categories of a catalog for real, matched by code.

Message, 3 operations

  • list_messagesList messagesGETLists messages of all chats or of one chat in a time window. Adds to BI data source costs, so save results. First page only: narrow from and to for more. Media links and locations are not returned.
  • send_messagesSend messagesPOSTSends messages to a chat for real; the contact receives them. On WhatsApp, after the chat's whatsAppWindowCloseDatetime (see get_chat) use trigger_intent with a template instead.
  • send_product_messageSend product messagePOSTSends a WhatsApp product message with catalog items to a chat for real; the contact receives it. The catalog must be connected to a Meta catalog.

Queue, 3 operations

  • get_queueGet queueGETReturns one attention queue with its name, slots and allowed transfer queues.
  • list_queuesList queuesGETLists the attention queues (agent teams) with their slots and allowed transfer queues. First page only.
  • update_queueUpdate queuePATCHChanges an attention queue for real (name, concurrent slots, allowed transfer queues). Leave out a field to keep its current value.

Ticket, 3 operations

  • create_ticketCreate ticketPOSTCreates a ticket for real. Read list_ticket_field_definitions first to fill customFields.
  • get_ticketGet ticketGETReturns one ticket by its code, with state, subject, content, assignment and field values.
  • list_ticketsList ticketsGETLists tickets created in the last N days, with state, subject, assignment and field values, a page at a time.

Typification, 3 operations

  • get_typificationGet typificationGETReturns one typification with its display name and queues.
  • list_typificationsList typificationsGETLists typifications (conversation classification labels agents apply) with their queues.
  • update_typificationUpdate typificationPATCHRenames a typification or changes its queues for real. Leave out a field to keep it.

Variable, 3 operations

  • get_variableGet variableGETReturns one variable definition (name, type, scope, visibility to agents).
  • list_variablesList variablesGETLists the bot's variable definitions (name, type, scope, visibility to agents).
  • update_variableUpdate variablePATCHChanges a variable definition for real (name, type, scope, how agents see it). Leave out a field to keep it.

Whatsapp account, 3 operations

  • get_whatsapp_accountGet whatsapp accountGETReturns one WhatsApp line with its alias, template namespace and business account id.
  • get_whatsapp_account_statusGet whatsapp account statusGETReturns a WhatsApp line's connection, display name, verification and quality status.
  • list_whatsapp_accountsList whatsapp accountsGETLists the WhatsApp phone lines with alias, template namespace and WhatsApp business account id.

Campaign, 2 operations

  • create_campaignCreate campaignPOSTCreates a notification campaign to group notifications. Sends nothing by itself.
  • list_campaignsList campaignsGETLists notification campaigns with their goal and status. First page only.

Catalog, 2 operations

  • create_catalogCreate catalogPOSTCreates an empty product catalog. Returns its id.
  • list_catalogsList catalogsGETLists the product catalogs with their title and connected platforms. First page only.

Channel, 2 operations

  • list_channelsList channelsGETLists the bot's channels (WhatsApp lines, Messenger, Instagram, Telegram and others) with their id, name and status. Channel ids are what chat tools take as channelId.
  • update_channelUpdate channelPATCHRenames a channel or turns it on or off for real; an inactive channel stops handling conversations. Leave out a field to keep it.

Entity, 2 operations

  • delete_entityDelete entityDELETEDeletes a whole bot entity and all its rows for real.
  • upsert_entity_itemsUpsert entity itemsPOSTCreates or updates rows of a bot entity (a lookup table the bot reads) for real.

Knowledge base, 2 operations

  • create_knowledge_baseCreate knowledge basePOSTCreates a knowledge base the bot's AI answers contacts from, using a file URL or website, for real (send no secrets); fails with a conflict if the name exists (use update_knowledge_base).
  • update_knowledge_baseUpdate knowledge basePUTUpdates the knowledge base with this name from new content (a file URL or a website to crawl) for real; the bot answers contacts from it, so send no secrets.

Notification result, 2 operations

  • get_notification_resultGet notification resultGETReturns one notification instance with its per-customer delivery detail, up to 2000 customers. Adds to BI data source costs. First page only.
  • list_notification_resultsList notification resultsGETLists sent notification instances with sent, delivered, read and answered counters, newest first, up to 500. Adds to BI data source costs. First page only; when nextPage is not null, narrow the from and to window to read the rest.

Price schema, 2 operations

  • list_price_schemasList price schemasGETLists a catalog's price schemas (per-zone price overrides of products). First page only.
  • list_zone_price_schemasList zone price schemasGETLists the price schemas (product price overrides) that apply to one zone of a catalog. First page only.

Reaction, 2 operations

  • add_reactionAdd reactionPOSTAdds an emoji reaction to a chat message for real; the contact sees it.
  • remove_reactionRemove reactionDELETERemoves the reaction previously added to a chat message, for real.

Billed conversation, 1 operation

  • list_billed_conversationsList billed conversationsGETLists one month's WhatsApp conversations with their billing info. Adds to the account's BI data source costs, so save the result. First page only.

Call, 1 operation

  • list_callsList callsGETLists calls in a time window (or for one chat), with their participants and timing. Recording links are not returned. Returns the first page only; when nextPage is not null, narrow the from and to window to read the rest.

Cart, 1 operation

  • checkout_cartCheckout cartPOSTChecks out the contact's active cart for real: closes it, computes totals and returns its details. Answers not found when the contact has no cart. WhatsApp only.

Chat variable, 1 operation

  • list_chat_variablesList chat variablesGETReturns the last value assigned to each variable of one chat within a time window.

Consumption, 1 operation

  • list_consumptionsList consumptionsGETReturns the account's consumption and spend for one month: balance, total spend and usage per product and project.

Contact, 1 operation

  • list_contactsList contactsGETLists contacts (names, phone numbers, emails, websites, linked chats), a page at a time. Filter by channel-id or platform, not both. Addresses, birthdays and pictures are not returned.

Notification, 1 operation

  • send_notificationSend notificationPOSTSends a notification (an intent, usually a WhatsApp template) to a list of contacts for real; every contact receives it and WhatsApp may bill each conversation.

Session, 1 operation

  • list_sessionsList sessionsGETLists chat sessions started in a time window, optionally with messages, final variables and AI analysis. Adds to BI data source costs, daily budget. First page only: narrow from and to for more.

Ticket field, 1 operation

  • list_ticket_field_definitionsList ticket field definitionsGETLists the ticket custom field definitions (id, name, type, valid options) used to fill customFields on create_ticket.

Use Botmaker from Claude Code, Cursor or Codex

Connect Botmaker in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Botmaker 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 Botmaker

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Botmaker once

    Add your Botmaker connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Botmaker integration FAQ

What can you do with the Botmaker integration?

LiveContext exposes 75 operations on Botmaker, covering product, zone, chat and intent.

Popular integrations

Browse the whole catalog