Integration

ChatArchitect WhatsApp API integration

ChatArchitect is a provider of the official WhatsApp Business API. An agent can send WhatsApp messages to a customer's phone number (text, image, audio, video, document, sticker, location, contact card, interactive list and quick-reply buttons), list the account's message templates by status, submit or delete a template, read the last 10 failed messages, post a notification as an incoming message, and register the webhook URLs that receive incoming messages and delivery events. Not included: the CSV export (it takes the credential as a query parameter), the payment-link route (undocumented beyond its title), and the app and user storage fields of the send route (integration configuration that can hold third-party tokens). Authentication is HTTP Basic with the APP ID as username and the APP SECRET as password, both issued by ChatArchitect support.

Connect ChatArchitect WhatsApp API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in ChatArchitect WhatsApp API.Built from the 9 ChatArchitect WhatsApp API tools below, on the connection you add once.

What you can do with ChatArchitect WhatsApp API

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Template, 4 operations

create_templateCreate templatePUTAgents: ask firstCreates a WhatsApp message template under the element name given in the path and submits it for approval (status PENDING until reviewed; check list_templates). Same fields as submit_template, without channel or destination.
delete_templateDelete templateDELETEAgents: ask firstDeletes the message template with the given element name. It can no longer be used to send messages; this cannot be undone.
list_templatesList templatesPOSTAgents: ask firstLists the account's WhatsApp message templates in three groups: templates (approved), templates_submitted (pending review) and templates_rejected. Call it to check a template's review status after submitting it.
submit_templateSubmit templatePOSTAgents: ask firstSubmits a new WhatsApp message template for approval (it starts PENDING; check list_templates). Send elementName, languageCode, category, templateType, content and example, as the vendor example does.

Message, 2 operations

send_messageSend messagePOSTAgents: ask firstSends a WhatsApp message to a customer's phone number (a real message to a real person, may be billed). payload.type picks the kind: text, image, audio, video, file, sticker, location, contact, list or quick_reply. Check that status is submitted.
send_text_messageSend text messagePOSTAgents: ask firstSends a plain-text WhatsApp message to a customer's phone number (a real message to a real person, which may be billed). A simpler form of send_message for text only. Check that status is submitted.

Failed message, 1 operation

list_failed_messagesList failed messagesPOSTAgents: ask firstReturns the last 10 messages that failed to send, each as one text line: timestamp, the recipient's phone number (personal data) and the failure reason (for example a session message to an inactive user with no matching template).

Notification, 1 operation

send_notificationSend notificationPOSTAgents: ask firstPosts a notification that ChatArchitect delivers as an incoming message (the vendor's wording), from the given source phone number under the given sender name. It reaches your connected inbox and integrations like a customer message.

Webhook, 1 operation

register_webhooksRegister webhooksPOSTAgents: ask firstSets the HTTPS URLs ChatArchitect posts incoming messages, delivery events and opt-in or opt-out events to, replacing the current registration. One URL for all, or one per type with webhook_separate true.

Use ChatArchitect WhatsApp API from Claude Code, Cursor or Codex

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

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