Integration

Sendiee integration

Sendiee is a WhatsApp, Instagram and Messenger marketing and AI-assistant platform built on Meta's official WhatsApp Cloud API (Meta Business Partner). Send approved WhatsApp templates or free-form messages (now or scheduled), track delivery, manage contacts, tags and custom fields, submit templates for Meta review, preview, run and cancel campaigns with delivery and cost reports, read chat history and the inbox, configure AI assistants and their lead categorisation, follow-ups and insights, route Teambox conversations to agents and teams, and read plan limits, billing history, wallet balance and channel health. Messages and campaigns reach real people, and outbound messages carry a Meta messaging cost. Left out: creating or editing assistant tools (a function tool's payload carries the credentials of the endpoint it calls) and tool argument schemas. Authentication is a Sendiee API key (Dashboard, API & Webhooks; scoped keys start with sk_ and need the matching scope), sent as a Bearer token.

Connect Sendiee How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Sendiee

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.

Assistant, 6 operations

create_assistantCreate assistantPOSTAgents: ask firstCreates an AI assistant that replies to customers. With channel_activate true it is bound to the channel at once and starts replying, taking the channel from any other assistant.
delete_assistantDelete assistantDELETEAgents: ask firstPermanently deletes an AI assistant and its edit history.
get_assistantGet assistantGETAgents: ask firstReturns one AI assistant with its channel, AI, behaviour, voice, audience, safety and rich-reply settings and attached tool IDs.
list_assistantsList assistantsGETAgents: ask firstLists the AI assistants of the organisation, last updated first, with channel, AI, behaviour, voice, safety and rich-reply settings and attached tool IDs.
toggle_assistantToggle assistantPOSTAgents: ask firstEnables or disables an AI assistant (its isActive flag); the change is recorded in its history.
update_assistantUpdate assistantPATCHAgents: ask firstChanges an AI assistant: only the fields sent change (abuseLimit and richReplies are replaced whole). Can also bind or disconnect its channel. Each call is saved in its history.

Lead category, 5 operations

create_lead_categoryCreate lead categoryPOSTAgents: ask firstCreates a lead category the AI can sort leads into. Counts against the plan's max_lead_categories limit.
delete_lead_categoryDelete lead categoryDELETEAgents: ask firstDeletes a lead category. Refused while contacts are in it, unless reassignTo names a category to move them to.
get_lead_categoryGet lead categoryGETAgents: ask firstReturns one lead category with its description, follow-up steps and follow-up switch.
list_lead_categoriesList lead categoriesGETAgents: ask firstLists the lead categories the AI sorts leads into, with their description, follow-up steps and whether follow-ups are disabled; meta says if categorisation is on.
update_lead_categoryUpdate lead categoryPATCHAgents: ask firstRenames a lead category or changes its description or follow-up switch. A rename relabels every contact in the category.

Lead insight, 5 operations

create_lead_insightCreate lead insightPOSTAgents: ask firstCreates a lead insight: a data field the AI extracts from each conversation and stores on the contact. Counts against the plan's max_ai_insights limit.
delete_lead_insightDelete lead insightDELETEAgents: ask firstPermanently deletes a lead insight (a data field the AI extracts from conversations).
get_lead_insightGet lead insightGETAgents: ask firstReturns one lead insight: key, name, value type, options and description.
list_lead_insightsList lead insightsGETAgents: ask firstLists the lead insights (audience segments): data fields the AI extracts from conversations onto contacts, with key, name, value type, options and description.
update_lead_insightUpdate lead insightPATCHAgents: ask firstChanges a lead insight's name, value type, options or description; only the fields sent change. The key cannot be changed.

Contact, 4 operations

get_contact_by_phoneGet contact by phonePOSTAgents: ask firstReturns the contact with a given phone number (spaces, +, dashes and parentheses are removed first). Personal data.
list_contactsList contactsGETAgents: ask firstLists the contacts of the organisation, up to 100 per page, with name, phone, email, address, lead category and custom fields (personal data).
search_contactsSearch contactsPOSTAgents: ask firstFinds contacts matching field values (partial, case-insensitive match on text fields such as name, phone, email, city; exact on others), up to 500 per page. Personal data.
upsert_contactUpsert contactPOSTAgents: ask firstCreates a contact, or updates the contact with the same phone number. Only the fields sent are written; isNew says which happened.

Custom field, 4 operations

create_custom_fieldCreate custom fieldPOSTAgents: ask firstCreates a custom contact field. Counts against the plan's max_custom_attributes limit.
delete_custom_fieldDelete custom fieldDELETEAgents: ask firstDeletes a custom field definition. Values already stored under its key on contacts are not removed.
list_custom_fieldsList custom fieldsGETAgents: ask firstLists the custom contact field definitions of the organisation: ID, name, key, type and dropdown options.
update_custom_fieldUpdate custom fieldPUTAgents: ask firstChanges a custom field's display name, type or options. Only the fields sent change; the fieldKey cannot be changed.

Tag, 4 operations

create_tagCreate tagPOSTAgents: ask firstCreates a contact tag. Names are unique per organisation; counts against the plan's max_contact_tags limit.
delete_tagDelete tagDELETEAgents: ask firstDeletes a contact tag from the organisation.
list_tagsList tagsGETAgents: ask firstLists the contact tags of the organisation, alphabetically, with their IDs.
rename_tagRename tagPUTAgents: ask firstRenames a contact tag. The new name must be unique within the organisation.

Tool, 4 operations

delete_toolDelete toolDELETEAgents: ask firstPermanently deletes an AI assistant tool, detaches it from every assistant using it and removes its version history.
get_toolGet toolGETAgents: ask firstReturns one AI assistant tool: name, description, type, enabled state, argument schema and IDs. Endpoint URLs and credentials are not returned.
list_toolsList toolsGETAgents: ask firstLists the AI assistant tools of the organisation, last updated first: name, description, type, enabled state and IDs. Endpoint URLs and credentials are not returned.
toggle_toolToggle toolPOSTAgents: ask firstTurns an AI assistant tool on or off. Leave isActive out to flip the current state. Assistants using it pick up the change on their next message.

Campaign, 3 operations

cancel_campaignCancel campaignPOSTAgents: ask firstCancels a campaign that has not completed: every pending recipient is skipped. Messages Meta already accepted still arrive.
create_campaignCreate campaignPOSTAgents: ask firstSends an APPROVED template to an audience as a campaign, now or at schedule_send_at; each message carries a Meta messaging cost. Set dryRun true first to validate and preview without sending.
list_campaignsList campaignsGETAgents: ask firstLists the campaigns of the organisation, up to 100 per page, with status, schedule and sent, delivered, read, failed and reply counts.

Conversation, 3 operations

assign_conversationAssign conversationPOSTAgents: ask firstAssigns a conversation to an agent and/or team: it moves into that agent's inbox live and they are notified. Team only: round-robin picks the agent.
list_conversationsList conversationsGETAgents: ask firstLists the inbox conversations, most recent message first: contact, last message preview, unread count, flags and AI summary (personal data).
unassign_conversationUnassign conversationPOSTAgents: ask firstRemoves the agent and team from a conversation, returning it to the unassigned pool; it leaves the previous agent's inbox at once. Its status is unchanged.

Lead followup, 3 operations

list_lead_followupsList lead followupsGETAgents: ask firstLists the lead follow-up steps: the organisation-wide default set and each category's own steps. Each step has a delay in seconds, a prompt and an active flag.
replace_default_lead_followupsReplace default lead followupsPUTAgents: ask firstReplaces the organisation-wide default follow-up steps (used by categories without their own) with the list sent.
replace_lead_category_followupsReplace lead category followupsPUTAgents: ask firstReplaces a lead category's follow-up steps with the list sent; an empty list removes them all.

Scheduled message, 3 operations

cancel_scheduled_messageCancel scheduled messageDELETEAgents: ask firstCancels a scheduled message so it is never sent. Only possible while its status is scheduled.
get_scheduled_messageGet scheduled messageGETAgents: ask firstReturns one scheduled message: recipient, due time, time zone, status, template and its body parameters.
list_scheduled_messagesList scheduled messagesGETAgents: ask firstLists the scheduled WhatsApp messages of the organisation, up to 100 per page, optionally by status (scheduled, sent, failed, cancelled).

Team, 3 operations

create_teamCreate teamPOSTAgents: ask firstCreates a Teambox team and adds the given agents and managers to it. Names are unique (case-insensitive); counts against the plan's max_teams.
list_teamsList teamsGETAgents: ask firstLists the shared-inbox (Teambox) teams with their members and managers (names and emails, personal data), plus the plan's team cap and usage.
update_teamUpdate teamPATCHAgents: ask firstChanges a Teambox team: only the fields sent change, but agentIds and managerIds replace the whole list. Set isActive false to take it out of routing.

Template, 3 operations

create_templateCreate templatePOSTAgents: ask firstSubmits a new WhatsApp template to Meta for review; it starts PENDING (approval takes minutes to 24 hours, check with list_templates). Capped at 2 per minute and 30 per day.
get_templateGet templateGETAgents: ask firstReturns one WhatsApp template, by Sendiee template ID or numeric Meta template ID: components, status, category, quality and group.
list_templatesList templatesGETAgents: ask firstLists the WhatsApp message templates of the account with their components, status and category; unarchived ones unless archived says otherwise.

Assistant version, 2 operations

list_assistant_historyList assistant historyGETAgents: ask firstLists the last 30 versions of an AI assistant: version number, change type, description, who changed it and when. create and config_update versions can be restored.
restore_assistant_versionRestore assistant versionPOSTAgents: ask firstRolls an AI assistant's configuration back to a prior create or config_update version; its channel and on/off state are kept. The restore is itself recorded as a version.

Conversation status, 2 operations

list_conversation_statusesList conversation statusesGETAgents: ask firstLists the inbox statuses of the workspace in display order (pending, open, resolved and custom ones): key, label, colour and flags. Use a key with set_conversation_status.
set_conversation_statusSet conversation statusPOSTAgents: ask firstMoves a conversation to another inbox status (for example resolved); the inbox updates live and the status-change automation event fires.

Lead segmentation, 2 operations

get_lead_segmentationGet lead segmentationGETAgents: ask firstReturns the whole lead segmentation setup (Lead Studio): settings, categories with their follow-ups, default follow-ups and insights (audience segments).
replace_lead_segmentationReplace lead segmentationPUTAgents: ask firstApplies a lead segmentation configuration: each top-level field sent is replaced (categories, defaultFollowups and audienceSegments replace the whole list); fields left out are kept.

Tool version, 2 operations

list_tool_historyList tool historyGETAgents: ask firstLists up to the last 30 versions of an AI assistant tool, newest first: version number, change type, description, source and when.
restore_tool_versionRestore tool versionPOSTAgents: ask firstRolls an AI assistant tool's configuration back to a prior version and records the restore as a new version. Its enabled state is not changed.

Agent, 1 operation

list_agentsList agentsGETAgents: ask firstLists the Teambox agents with name, email (personal data), role, teams and membership status (active or invited), plus the plan's seat cap. Only active agents can be assigned.

Assistant option, 1 operation

get_assistant_optionsGet assistant optionsGETAgents: ask firstReturns the values create_assistant and update_assistant accept: AI providers, models per provider, platforms, voice providers, TTS models and voices, and numeric ranges.

Billing plan, 1 operation

get_billing_planGet billing planGETAgents: ask firstReturns the organisation's plan, its subscription, every plan limit with current usage and remaining headroom, and the feature flags. Check it before bulk operations.

Campaign audience, 1 operation

preview_campaign_audiencePreview campaign audiencePOSTAgents: ask firstCounts the audience a campaign would reach (opt-outs, undeliverable, a 10-contact sample) without sending. In raw contacts mode the phones are added to your contacts.

Campaign report, 1 operation

get_campaign_reportGet campaign reportGETAgents: ask firstReturns one campaign's report: delivery counters, delivery, read, reply and click rates (percent), button clicks, cost by category and country, and failure reasons.

Channel status, 1 operation

get_channel_statusGet channel statusGETAgents: ask firstChecks the WhatsApp, Instagram and Messenger channels live with Meta: connection status (connected, token_expired, permission_denied...), quality rating, tier and Meta errors.

Chat message, 1 operation

get_chat_historyGet chat historyGETAgents: ask firstReturns the messages exchanged with one contact, newest first (personal data), and whether its 24-hour reply window is open. Pass phone or contactId; page with before.

Contact field, 1 operation

list_contact_fieldsList contact fieldsGETAgents: ask firstLists the contact fields of the organisation: the 19 built-in fields and the custom fields, with their key, label and type. Use it before reading or writing contact data.

Conversation assignment, 1 operation

get_conversation_assignment_historyGet conversation assignment historyGETAgents: ask firstReturns a conversation's audit trail, oldest first (last 200 events): assignments, unassignments and status changes, with actor and time.

Daily summary, 1 operation

list_daily_summariesList daily summariesGETAgents: ask firstReturns daily AI conversation rollups per platform: conversations, messages, media, audio seconds, tools used, model usage and cost (in thousandths of a US dollar).

Lead segmentation setting, 1 operation

update_lead_segmentation_settingsUpdate lead segmentation settingsPATCHAgents: ask firstChanges only the lead segmentation settings (switches, delay, model, prompts); categories, follow-ups and insights are untouched. Only the fields sent change.

Message status, 1 operation

get_message_statusGet message statusGETAgents: ask firstReturns the delivery status of a sent WhatsApp message (accepted, sent, delivered, read or failed), by the messageId a send tool returned.

Payment, 1 operation

list_paymentsList paymentsGETAgents: ask firstLists the organisation's payments (wallet top-ups, subscription purchases, auto-recharges, renewals): amounts, tax breakdown, status and gateway.

Pipeline snapshot, 1 operation

list_pipeline_snapshotsList pipeline snapshotsGETAgents: ask firstReturns daily lead-pipeline snapshots: contacts per lead category, new contacts per platform, opt-outs and never-categorised contacts (kept 365 days).

Subscription, 1 operation

list_subscriptionsList subscriptionsGETAgents: ask firstLists every subscription record of the organisation: plan, billing cycle, status, payment status, dates and amount paid.

Tool run, 1 operation

list_tool_runsList tool runsGETAgents: ask firstLists recent calls of an AI assistant tool by assistants (kept 15 days): status, error, duration and HTTP status. Arguments, results and request URLs are not returned.

Wallet balance, 1 operation

get_wallet_balanceGet wallet balanceGETAgents: ask firstReturns the organisation's wallet balance in USD (up to 4 decimals) and whether the wallet is active.

Whatsapp message, 1 operation

send_messageSend messagePOSTAgents: ask firstSends a free-form WhatsApp message (text, image, document, audio or video) to a real recipient now, or at scheduledAt. Only works within 24 hours of the recipient's last message.

Whatsapp template message, 1 operation

send_template_messageSend template messagePOSTAgents: ask firstSends an approved WhatsApp template message to a real recipient now, or at scheduledAt; outbound messages carry a Meta messaging cost. Templates are not limited by the 24-hour window.

Use Sendiee from Claude Code, Cursor or Codex

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

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