Integration

8x8 Messaging Apps integration

8x8 Messaging Apps (part of 8x8 Connect) sends business messages over WhatsApp, Viber, RCS, LINE, Zalo and other chat apps through one API, with SMS fallback. An agent can send a text, media, location, interactive or WhatsApp template message to one user or in batch, schedule and cancel messages, read a message's delivery status, mark an inbound message as read, show a typing indicator, send LINE Official Notifications, register, list and delete WhatsApp message templates, create, update, publish, preview and deprecate WhatsApp Flows, check WhatsApp call permission, export message logs, read monthly WhatsApp usage, and manage the account's Messaging Apps webhooks. Messages are billed per message and channel. The file upload and download routes are not exposed. Authentication is an API key from the 8x8 Connect portal sent as a Bearer token; the connection also holds the account id, the subaccount id used to send, and the region domain of the account (8x8.com for Asia Pacific, 8x8.uk for Europe, us.8x8.com for North America, 8x8.id for Indonesia).

Connect 8x8 Messaging Apps How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in 8x8 Messaging Apps.Built from the 28 8x8 Messaging Apps tools below, on the connection you add once.

What you can do with 8x8 Messaging Apps

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.

Whatsapp flow, 8 operations

create_whatsapp_flowCreate whatsapp flowPOSTCreate a WhatsApp Flow (an in-chat form) from a Flow JSON definition or by cloning another flow. Stays a draft unless publish is true. Returns the flow id.
delete_whatsapp_flowDelete whatsapp flowDELETEDelete a WhatsApp Flow that has not been published.
deprecate_whatsapp_flowDeprecate whatsapp flowPOSTDeprecate a published WhatsApp Flow: it stays usable by existing integrations but is no longer recommended.
get_whatsapp_flowGet whatsapp flowGETGet one WhatsApp Flow: name, status, categories, a link to its Flow JSON (flowJsonUrl) and any validation errors.
list_whatsapp_flowsList whatsapp flowsGETList the WhatsApp Flows of a channel with their status.
preview_whatsapp_flowPreview whatsapp flowGETGet a preview URL to view and try a WhatsApp Flow before publishing it.
publish_whatsapp_flowPublish whatsapp flowPOSTPublish a draft WhatsApp Flow so it can be sent in conversations. A published flow can no longer be edited.
update_whatsapp_flowUpdate whatsapp flowPUTUpdate a WhatsApp Flow that is still a draft: name, categories, Flow JSON, endpoint URI. Leave out a field to keep it.

Message, 4 operations

cancel_scheduled_messageCancel scheduled messageDELETECancel a scheduled chat app message that has not been sent yet, by its umid.
get_messageGet messageGETGet a chat app message by its umid. Returns data[], message records each with channel, direction, delivery status (state, detail, error), recipient, content type and content, and timestamps.
mark_message_readMark message readPOSTMark an inbound chat app message as read, so the user sees the read receipt.
send_messageSend messagePOSTSend one chat app message (WhatsApp, Viber, RCS, LINE...) to one user, billed per message. Returns umid (pass it to get_message for the delivery status) and the accepted status.

Message log export, 3 operations

cancel_message_log_exportCancel message log exportDELETECancel a message log export job that has not finished.
get_message_log_exportGet message log exportGETGet a message log export: status queued, running, succeeded, failed, cancelled, empty or error; when succeeded, data[] holds the CSV download links, valid until expires.
start_message_log_exportStart message log exportPOSTStart an export of the subaccount's chat app message logs (CSV). Returns jobId: call get_message_log_export until status is succeeded, then download the links in data.

Webhook, 3 operations

delete_webhooksDelete webhooksDELETERemove the Messaging Apps webhook configured for each listed subAccountId. * targets only the all-subaccounts webhook; it is not a wildcard that deletes every webhook.
list_webhooksList webhooksGETList the Messaging Apps webhooks of the account (inbound messages and delivery receipts): subaccount scope, url and enabled flag.
set_webhooksSet webhooksPOSTCreate or replace Messaging Apps webhooks for inbound messages and delivery receipts: each item names a subAccountId (or * for every subaccount) and a url. Answers no content.

Message batch, 2 operations

cancel_message_batchCancel message batchDELETECancel the messages of a scheduled batch that have not been sent yet. Returns cancelledCount.
send_message_batchSend message batchPOSTSend personalised chat app messages in batch (each billed): messages[] holds per-recipient parts (at least user), template the parts shared by all. Returns batchId and accepted and rejected counts.

Message template, 2 operations

delete_message_templateDelete message templateDELETEDelete a registered message template from the channel, by its name.
list_message_templatesList message templatesGETList the message templates registered on a channel (WhatsApp, Viber) with their language, category, components and approval status.

Line notification, 1 operation

send_line_notificationSend line notificationPOSTSend one LINE Official Notification (a structured LINE message: title, company, emphasis, list, explanation, actions), with optional SMS fallback. Billed per message. Returns umid and status.

Line notification batch, 1 operation

send_line_notification_batchSend line notification batchPOSTSend LINE Official Notifications in batch (each billed): messages[] with at least user per recipient and the notification content. Returns batchId and counts.

Message usage, 1 operation

get_message_usageGet message usageGETGet the account's monthly WhatsApp message usage for one closed billing period (YYYY-MM, from 2026-02, at most 6 months back), optionally grouped by subaccount, channel, category or country.

Typing indicator, 1 operation

send_typing_indicatorSend typing indicatorPOSTShow a typing indicator to a user on WhatsApp or RCS while a reply is prepared. umid must be an inbound message received within the last 2 hours.

Whatsapp call permission, 1 operation

get_whatsapp_call_permissionGet whatsapp call permissionGETCheck whether the business may call a WhatsApp user: status (temporary, permanent or not_granted) and which actions (send a call permission request, start a call) are allowed.

Whatsapp template, 1 operation

create_whatsapp_templateCreate whatsapp templatePOSTRegister a WhatsApp message template for approval by WhatsApp: name, language, category (UTILITY, MARKETING or AUTHENTICATION) and components. Follow its status with list_message_templates.

Use 8x8 Messaging Apps from Claude Code, Cursor or Codex

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

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