Integration

Chatbase integration

Chatbase builds AI support agents trained on your own content. With this API you can create, configure, clone and delete agents, chat with an agent and continue its conversations, add and update the text, Q and A, website and file knowledge sources it answers from, read, search and export its conversations from every channel, run the helpdesk (tickets, replies, statuses, teams) and send approved WhatsApp templates from the agent's connected numbers. Chatting consumes the plan's message credits. Authentication is a workspace API key (Workspace settings, API keys) sent as a Bearer token; API v2 needs the Basic plan or higher, and the limit is 1,000 requests per 10 seconds per key. Not exposed: streaming replies, voice sessions, the two deprecated no-op routes (train, restore source), email notification recipients, and ticket attachment download links.

Connect Chatbase How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Chatbase

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.

Conversation, 8 operations

delete_conversationDelete conversationDELETEDeletes a conversation from any channel (API, widget, WhatsApp...): it disappears from chat logs and from every API response.
delete_user_conversationsDelete user conversationsDELETEDeletes every conversation of one user under an agent, from all channels; they disappear from chat logs and API responses. Returns deletedCount.
export_conversationsExport conversationsGETExports an agent's conversations from every channel (widget, API, WhatsApp...) with full message history, 20 per page. Pass conversationId to read one conversation from any channel.
get_conversationGet conversationGETReturns one API-created conversation with its most recent messages and a cursor for older ones (list_conversation_messages). For widget or WhatsApp conversations use export_conversations with conversationId.
list_conversationsList conversationsGETLists conversations created through the API for an agent, by creation date, 20 per page (up to 100). Widget, WhatsApp and other channels are not included: use export_conversations or search_conversations.
list_user_conversationsList user conversationsGETLists the API-created conversations of one of your users (the userId passed to chat_with_agent), most recently active first, 20 per page. Other channels: search_conversations with userId.
search_conversationsSearch conversationsGETSearches an agent's conversations from every channel by text (query) and filters (sentiment, topic, source, escalation, feedback, tools, dates). Returns ids and snippets; read messages with export_conversations.
update_conversation_statusUpdate conversation statusPATCHSets a conversation's state: paused stops AI replies (messages are still recorded), ended ends it, ongoing resumes it. Only API conversations can be resumed from ended, and not on conversation-based billing.

Agent, 7 operations

clone_agentClone agentPOSTCreates a new, independent copy of an agent with all its sources except Notion pages. Returns the new agent id and pendingSteps. Counts toward the plan's agent limit (AGENT_LIMIT_REACHED, 403).
create_agentCreate agentPOSTCreates a new agent. Give a url to have that site added as a link source and trained automatically. Returns id; check pendingSteps (ADD_SOURCE) for a source that could not be added, then use create_source.
delete_agentDelete agentDELETEPermanently deletes an agent and all its sources, and disconnects its integrations (Slack, WhatsApp and others). The vendor states it cannot be undone.
get_agentGet agentGETReturns one agent with its settings: instructions, per-channel instruction overrides, model, temperature, visibility, embed domains, credit limit and usage, spam, rate-limit, voice and widget style settings, training status.
list_agentsList agentsGETLists the agents (chatbots) of the workspace, 20 per page by default (up to 100). Each item gives id, name, model, training status and usage; read one agent's full settings with get_agent.
update_agentUpdate agentPUTChanges an agent's settings: name, instructions, per-channel instructions, model, temperature, visibility, embed domains, messages, credit limit, rate limits, spam, voice, blocked countries. Only fields sent change.
update_agent_auto_retrainUpdate agent auto retrainPUTTurns automatic retraining of an agent on (retrains every 7 days) or off. The agent must have been trained once (else AGENT_NOT_TRAINED, 409) and the plan must be Basic or higher.

Source, 7 operations

create_file_sourceCreate file sourcePOSTUploads a PDF, DOC, DOCX or TXT file (up to 20 MB) as a knowledge source of an agent; it trains immediately. Returns the new source.
create_sourceCreate sourcePOSTAdds a text, Q and A, or website (link) knowledge source; it trains at once, returned untrained then trained. text needs name and content; qna needs name, questions, answer; link needs url and linkType.
delete_sourceDelete sourceDELETEDeletes a knowledge source; its knowledge is removed from the agent immediately. Returns the source with its final status (deleted, or toBeDeleted while the purge finishes).
get_sourceGet sourceGETReturns one knowledge source with its type, name, size, status (untrained, trained, updated, failed and others) and, for links, crawl settings and child counts.
list_sourcesList sourcesGETLists an agent's knowledge sources (link, file, qna, text, notionPage) with type, size and training status, 20 per page. Link crawls appear as one parent with child counts; ticket sources are excluded.
update_file_sourceUpdate file sourcePUTReplaces the file of a file source, renames it, or both (send at least one of name and file). A new file retrains the source.
update_sourceUpdate sourcePUTChanges a text, Q and A or link source; a content change retrains it at once (status updated until live). A link's URL cannot change: delete and recreate it. Files use update_file_source.

Ticket, 5 operations

create_ticketCreate ticketPOSTCreates a real helpdesk ticket for a customer (by email); description becomes the customer's first message. Auto-assigned by the routing rules unless an assignee or team is given. Returns the ticket and its number.
get_ticketGet ticketGETReturns one helpdesk ticket by its per-agent number: subject, status, priority, assignee, team, channel, customer (name, email, phone) and dates.
list_ticketsList ticketsGETLists an agent's helpdesk tickets, newest update first, 20 per page (up to 100), filterable by status category, channel, assignee, team, priority and creation dates. Read a thread with list_ticket_messages.
search_ticketsSearch ticketsPOSTSearches the messages of an agent's tickets with free text and returns matching tickets ranked by relevance, up to limit (1 to 50, default 20). Not paginated. Read-only.
update_ticketUpdate ticketPATCHChanges a ticket's status, assignee, team or priority; only fields sent change, and at least one is needed. Fields are written independently, so a 500 can leave a partial update.

Message, 2 operations

chat_with_agentChat with agentPOSTSends a message to an agent and returns its full reply (data.parts) and data.metadata.conversationId; pass that id back to continue. Consumes message credits (data.metadata.usage.credits); 402 when none are left.
retry_messageRetry messagePOSTRegenerates the agent's answer: truncates the conversation at the given message, then re-sends the user message before it. Later messages are removed. Consumes message credits like chat_with_agent.

Agent style, 1 operation

update_agent_stylesUpdate agent stylesPUTChanges the look of an agent's chat widget and Center Stage page: theme, colors, display name, launcher position, auto-open delay, placeholder, footer, notice and which buttons show. Returns success.

Conversation message, 1 operation

list_conversation_messagesList conversation messagesGETLists the messages of an API-created conversation, newest page first and chronological within a page, 20 per page (up to 100). The cursor from get_conversation also works here.

Health, 1 operation

check_healthCheck healthGETChecks that the Chatbase API is up; needs no key. Returns status and a timestamp.

Helpdesk team, 1 operation

list_helpdesk_teamsList helpdesk teamsGETLists the helpdesk teams of an agent, by creation date, with their member count; one is the default. Team ids feed create_ticket, update_ticket and list_tickets teamId.

Message feedback, 1 operation

update_message_feedbackUpdate message feedbackPATCHSets feedback on an assistant message (positive or negative) as a visitor would. Message ids come from list_conversation_messages or chat_with_agent.

Source summary, 1 operation

get_sources_summaryGet sources summaryGETReturns, per source type, how many sources an agent has and their total size, plus shouldRetrain when the knowledge base has changes not yet reflected.

Ticket message, 1 operation

list_ticket_messagesList ticket messagesGETLists a ticket's thread, oldest first by default, 20 per page: replies (seen by the customer), internal notes and, on request, system events (status, assignment, emails sent). Attachment links are not returned.

Ticket reply, 1 operation

create_ticket_messageCreate ticket messagePOSTPosts a real reply to a ticket, sent to the customer, attributed to a team member (authorId or authorEmail). Recorded at once, delivered asynchronously; it may change the ticket status.

Ticket status, 1 operation

list_ticket_statusesList ticket statusesGETLists the active ticket statuses of an agent's helpdesk by category (new, on_you, on_customer, on_hold, closed, cancelled), one default per category. Ids feed create_ticket and update_ticket statusId.

Tool result, 1 operation

submit_tool_resultSubmit tool resultPOSTSends the result of a client-side action the agent asked for (a tool-call part in a chat_with_agent reply). Then call chat_with_agent with the same conversationId and no message so the agent continues.

Whatsapp message, 1 operation

send_whatsapp_templateSend whatsapp templatePOSTSends a real WhatsApp message to a real person's phone number from the agent's connected business number; replies continue in the returned conversationId. Meta may bill it; the recipient must have opted in.

Whatsapp template, 1 operation

list_whatsapp_templatesList whatsapp templatesGETLists the approved WhatsApp templates of an agent's connected Business Accounts, with the variables each needs and the numbers (senders) that can send them. Use before send_whatsapp_template.

Use Chatbase from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Chatbase once
Add your Chatbase 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.