Integration

Sakari integration

Sakari is an SMS and MMS business messaging platform. Send text messages to contacts, conversations or tagged groups, read message history and conversations, manage contacts and message templates, run and inspect campaigns, drip campaigns and workflows, track short links, lead forms and calls, manage webhooks and check balance and pricing. Creating or editing workflows, drip campaigns and autoresponders, editing contacts, templates and campaigns, meeting scheduling, and billing, plan and top-up changes are not exposed. Authentication is OAuth2 client credentials: the client id and secret and the account id come from the API credentials in the Sakari Hub account settings.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Sakari

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.

Form, 5 operations

  • create_formCreate formPOSTCreates a lead form with a name, optionally cloned from a form template.
  • delete_formDelete formDELETEDeletes a lead form by id.
  • get_formGet formGETReturns one lead form by id: name, impressions, conversions and when it was activated.
  • list_formsList formsGETLists the account's lead forms, each with impressions, conversions and when it was activated; q searches, orderBy sorts.
  • update_formUpdate formPUTRenames a lead form; name is its new name.

Template, 5 operations

  • create_templateCreate templatePOSTSaves a reusable message template: a name, its type (SMS or Web), the message text with optional placeholders such as {{{firstName}}}, and optional media.
  • delete_templateDelete templateDELETEDeletes a message template by id.
  • get_templateGet templateGETReturns one message template by id: name, type, text and media.
  • list_form_templatesList form templatesGETLists the lead form templates a new form can be cloned from.
  • list_templatesList templatesGETLists the saved message templates, with offset and limit for paging; filter by part of the name.

Campaign, 4 operations

  • create_campaignCreate campaignPOSTCreates a campaign from a trigger (code M manual, S scheduled, FU file upload or V2), contact filters (contact ids, tags, attributes) and the message template.
  • delete_campaignDelete campaignDELETEDeletes a campaign by id.
  • get_campaignGet campaignGETReturns one campaign by id: trigger, filters, template, media, schedule, next execution and last execution.
  • list_campaignsList campaignsGETLists campaigns, with offset and limit for paging; filter by part of the name. Each has its trigger, filters, template, schedule and last execution.

Contact, 4 operations

  • create_contactCreate contactPOSTCreates a contact from a mobile number (with its country) and optional name, email, lists and custom attributes. mergeStrategy says what happens when a contact with that mobile number already exists.
  • delete_contactDelete contactDELETEDeletes a contact by id from the account.
  • get_contactGet contactGETReturns one contact by id: name, email, mobile number details, lists it belongs to with opt-in and opt-out dates, custom attributes, and blocked status.
  • list_contactsList contactsGETLists contacts with offset and limit for paging; filter by part of the first name, last name, mobile number or email, or by tag.

Autoresponder, 3 operations

  • delete_autoresponderDelete autoresponderDELETEDeletes an autoresponder by id.
  • get_autoresponderGet autoresponderGETReturns one autoresponder by id: the incoming text it matches, the reply it sends, its schedule type and group.
  • list_autorespondersList autorespondersGETLists the account's autoresponders: the incoming text each one matches and the reply it sends.

Deactivate, 3 operations

  • deactivate_drip_campaignDeactivate drip campaignPUTDeactivates a drip campaign by id.
  • deactivate_formDeactivate formPUTDeactivates a lead form by id and returns it.
  • deactivate_workflowDeactivate workflowDELETEDeactivates a workflow by id; success says whether it worked.

Dripcampaign, 3 operations

  • delete_drip_campaignDelete drip campaignDELETEDeletes a drip campaign by id.
  • get_drip_campaignGet drip campaignGETReturns one drip campaign by id: trigger, messages, whether it is active and its stats.
  • list_drip_campaignsList drip campaignsGETLists the account's drip campaigns, with offset and limit for paging.

Execution, 3 operations

  • get_workflow_executionGet workflow executionGETReturns one workflow execution with its status, version, start and end and every step it went through.
  • list_drip_campaign_executionsList drip campaign executionsGETLists the contacts that entered a drip campaign, with their status and entry date.
  • list_workflow_executionsList workflow executionsGETLists the executions of a workflow with status, version, start and end; filter by contact, status or date range.

Link, 3 operations

  • delete_linkDelete linkDELETEDeletes a tracked short link by id.
  • get_linkGet linkGETReturns one tracked short link by id: destination URL, short URL, tracking settings and click stats (total, unique, click-through rate).
  • list_linksList linksGETLists the account's tracked short links, each with its destination URL, short URL and click stats; q searches across fields.

Message, 3 operations

  • get_messageGet messageGETReturns one message by id: text, direction (outgoing), status, segments, price, the contact and conversation, and any error.
  • list_messagesList messagesGETLists messages sent and received on the account, with offset and limit for paging; filter by contactId or conversationId. Each message has its text, direction, status, segments, price and contact.
  • send_messagesSend messagesPOSTSends an SMS or MMS to one or many recipients in one call: contacts (each with a mobile number), existing conversation ids, or contacts matched by tags. template is the text, with optional placeholders such as {{{firstName}}}.

Webhook, 3 operations

  • create_webhookCreate webhookPOSTSubscribes a URL to account events (message received, sent or status, contact created, updated or removed, opt-ins and opt-outs, conversation started); Sakari posts each event to it.
  • delete_webhookDelete webhookDELETERemoves the webhook subscription for the given URL.
  • list_webhooksList webhooksGETLists the account's webhook subscriptions: destination URL and event types.

Workflow, 3 operations

  • delete_workflowDelete workflowDELETEDeletes a workflow by id.
  • get_workflowGet workflowGETReturns one workflow by id with its versions (id, name, active and last active dates).
  • list_workflowsList workflowsGETLists the account's workflows (automations), with offset and limit for paging.

Activate, 2 operations

  • activate_drip_campaignActivate drip campaignPUTActivates a drip campaign by id.
  • activate_formActivate formPUTActivates a lead form by id and returns it.

Call, 2 operations

  • get_callGet callGETReturns one call by id: direction, status, contact, Sakari phone number, user, duration and whether it left a voicemail or recording.
  • list_callsList callsGETLists calls (call history) with offset and limit for paging; filter by conversation, Sakari phone number, contact, user, group, direction, status or date range.

Conversation, 2 operations

  • get_conversationGet conversationGETReturns one conversation by id: the contact, the Sakari phone number, the last message, unread messages and when it was closed.
  • list_conversationsList conversationsGETLists conversations with offset and limit for paging. Each has the contact, the last message, unread messages and closed date.

Source, 2 operations

  • get_link_sourceGet link sourceGETReturns one source of a tracked link with its click stats (total, unique, click-through rate).
  • list_link_sourcesList link sourcesGETLists the sources (where the link was sent from) of a tracked link, each with its click stats.

Workflowtemplate, 2 operations

  • get_workflow_templateGet workflow templateGETReturns one workflow template by id: name, description, status, tags, groups and needed integrations.
  • list_workflow_templatesList workflow templatesGETLists the workflow templates Sakari offers, with name, description, status, tags and the integrations they need.

Analytic, 1 operation

  • get_form_analyticsGet form analyticsGETReturns the impressions and conversions of a lead form between start and end, in total and per date.

Availablephonenumber, 1 operation

  • search_available_phone_numbersSearch available phone numbersGETSearches phone numbers available to add to the account, by country, type, area code, postal code, features or digits they contain. Returns each number with its price and features.

Balance, 1 operation

  • get_balanceGet balanceGETReturns the account balance with its country, a segment count and the price per message segment.

Clone, 1 operation

  • duplicate_workflowDuplicate workflowPOSTCreates a copy of a workflow, optionally from a given version.

Close, 1 operation

  • close_conversationClose conversationPUTCloses an open conversation by id and returns it.

Conversion, 1 operation

  • get_form_conversionsGet form conversionsGETLists the submissions of a lead form between start and end: submitted fields, page URL, IP and the resulting contact.

Duplicate, 1 operation

  • duplicate_drip_campaignDuplicate drip campaignPOSTCreates a copy of a drip campaign and returns it.

Metric, 1 operation

  • get_workflow_version_metricsGet workflow version metricsGETReturns a summary of the edges travelled in a workflow version between start and end: a total and a count per edge.

Migrate, 1 operation

  • convert_drip_campaign_to_workflowConvert drip campaign to workflowPUTTransforms a drip campaign into a workflow.

Plan, 1 operation

  • get_planGet planGETReturns the account's current plan: name, price, commitment, included credit, billing frequency and per-country pricing.

Price, 1 operation

  • get_pricingGet pricingGETReturns the price per message segment for a plan, by country, from either a monthly credit or a commitment amount (pass one of the two, not both).

Publish, 1 operation

  • publish_workflowPublish workflowPOSTPublishes a workflow by id; success says whether it worked.

Quickcampaign, 1 operation

  • create_and_run_campaignCreate and run campaignPOSTCreates and immediately executes a campaign: a name, the contact list to send to (listId), the group to send from (groupId), the message with optional media, and an optional send time (sendAt). Returns the campaign and its job.

Recording, 1 operation

  • download_call_recordingDownload call recordingGETDownloads a call recording as an audio file (WAV).

Sharefile, 1 operation

  • share_fileShare filePOSTUploads a file and returns a short link to it, to use in a message or as the media of an MMS, with the date the link expires.

Stat, 1 operation

  • get_link_source_statsGet link source statsGETReturns the statistics of one source of a tracked link, as a list of date and value pairs.

Version, 1 operation

  • get_workflow_versionGet workflow versionGETReturns one version of a workflow: name, definition (nodes and edges), and when it was active.

Use Sakari from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Sakari once

    Add your Sakari connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Sakari integration FAQ

What can you do with the Sakari integration?

LiveContext exposes 69 operations on Sakari, covering form, template, campaign and contact.

Popular integrations

Browse the whole catalog