Integration

SendZen integration

SendZen is a WhatsApp Business Platform (Cloud API) provider for developers. An agent can send WhatsApp messages from a connected number (text, image, video, audio, document, reply buttons and approved templates), mark received messages as read with a typing indicator, download media users sent, list, create and delete message templates, list projects and their WhatsApp Business Accounts and numbers, read Meta's account details, read and update the business profile, search the last 7 days of event logs (inbound messages, delivery statuses, other events), and create, list and delete webhook configurations. Not included: the resumable media upload routes and the webhook update route (their request bodies are undocumented), and every webhook signing secret (never returned, never set). Authentication is a SendZen API key from the SendZen dashboard, sent as a Bearer token in the Authorization header.

Connect SendZen How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with SendZen

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.

Webhook config, 5 operations

create_webhook_configCreate webhook configPOSTAgents: ask firstCreates a webhook configuration: SendZen posts the chosen events of a WhatsApp Business Account to the URL. This tool sets no signing secret, so deliveries cannot be verified with a signature.
delete_webhook_configDelete webhook configDELETEAgents: ask firstDeletes a webhook configuration: SendZen stops posting its events to the URL.
get_webhook_configGet webhook configGETAgents: ask firstReturns one webhook configuration: URL, name, project, WABA, subscribed events, timeout and active flag. Its signing secret is not returned.
list_project_webhook_configsList project webhook configsGETAgents: ask firstLists the webhook configurations of one project: URL, name, WABA, subscribed events, timeout and active flag. Signing secrets are not returned.
list_webhook_configsList webhook configsGETAgents: ask firstLists every webhook configuration of the account: URL, name, project, WABA, subscribed events, timeout and active flag. Signing secrets are not returned.

Project, 4 operations

create_projectCreate projectPOSTAgents: ask firstCreates a SendZen project (a container for WhatsApp Business Accounts and webhooks) and returns it with its project_id.
get_projectGet projectGETAgents: ask firstReturns one SendZen project: name, description, client identifier, type, sandbox flag and creation time.
list_projectsList projectsGETAgents: ask firstLists the SendZen projects of the account with their id, name, description, client identifier, type, sandbox flag and creation time.
update_projectUpdate projectPUTAgents: ask firstUpdates a SendZen project. Read it first with get_project and send every field to keep (name, description, client identifier, type): fields left out may be cleared.

Message template, 3 operations

create_message_templateCreate message templatePOSTAgents: ask firstCreates a WhatsApp message template on a WhatsApp Business Account and submits it to Meta's review; it can be sent once approved (check with list_message_templates).
delete_message_templateDelete message templateDELETEAgents: ask firstDeletes a message template of a WhatsApp Business Account: by name (every language of that name), or one language with name plus hsm_id. This cannot be undone.
list_message_templatesList message templatesGETAgents: ask firstLists the message templates of a WhatsApp Business Account with their id, name, language, category, review status and components, optionally filtered by name, page by page with the before and after cursors.

Business profile, 2 operations

get_business_profileGet business profileGETAgents: ask firstReturns the WhatsApp business profile of a connected number: the fields you name among about, address, description, email, profile_picture_url, websites and vertical.
update_business_profileUpdate business profilePOSTAgents: ask firstUpdates the WhatsApp business profile shown to users of a connected number (about, address, description, email, websites, industry). Fields left out keep their value.

Waba, 2 operations

get_wabaGet wabaGETAgents: ask firstReturns a WhatsApp Business Account's details as Meta holds them (name, currency, time zone and other fields you name in fields).
list_wabasList wabasGETAgents: ask firstLists the projects of the account with their WhatsApp Business Accounts: WABA ID, business name, phone number, phone number ID and status. Call it first to get the ids the other tools need.

Event log, 1 operation

list_logsList logsGETAgents: ask firstLists event logs of the last 7 days: inbound messages, message statuses (sent, delivered, read, failed) and other events, with their raw WhatsApp payload (personal data), 20 per page; pass next_page_token to page.

Media, 1 operation

download_mediaDownload mediaGETAgents: ask firstDownloads a media file a user sent (image, video, audio, document or sticker) and returns it as a file. Pass the exact media URL from the incoming webhook or list_logs payload. User media is personal data.

Message, 1 operation

send_messageSend messagePOSTAgents: ask firstSends a WhatsApp message from a connected number to a person: text, image, video, audio, document, reply buttons or an approved template. It reaches a real person; a non-template message fails once 24 hours have passed since the user last wrote.

Message read status, 1 operation

mark_message_readMark message readPOSTAgents: ask firstMarks a received WhatsApp message as read (blue ticks). With typing_indicator it also shows the user a typing indicator while you prepare the reply. Pass the wamid of the inbound message.

Use SendZen from Claude Code, Cursor or Codex

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

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