What can you do with the Evolution API integration?

LiveContext exposes 19 operations on Evolution API, covering instance, message, group and webhook. Common uses include sending a delivery address to a driver, delivering an invoice PDF over WhatsApp and moving an instance to a different phone number.

LiveContext

All integrations

Evolution API integration

Evolution API v2, the self-hosted WhatsApp gateway. Manage instances (create, connect through a QR code or pairing code, read connection state, log out, delete), send messages (text, media, location), check whether phone numbers are on WhatsApp, mark messages as read, query the stored chats, contacts and messages of an instance, create groups and manage their participants, and configure the webhook that pushes incoming events. Every call is scoped to a named instance, and the server is your own, so the host is part of the credential.

19 toolsAPI keyAPI docs

Connect Evolution API How integrations work

Common Evolution API use cases

sending a delivery address to a driver
delivering an invoice PDF over WhatsApp
moving an instance to a different phone number
decommissioning a sender that is no longer used
adding a colleague to an existing customer group
guarding a send step behind a connectivity check
notifying a customer on WhatsApp from a workflow
listing recent conversations to pick one to answer
re-pairing an instance whose session was logged out
discovering the instance name before sending a message

What you can do with Evolution 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.

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

Instance, 6 operations

GETconnect_instance
Issues a fresh pairing QR code for an instance that is not linked yet.
POSTcreate_instance
Creates a named WhatsApp instance and returns the QR code needed to pair a phone.
DELETEdelete_instance
Permanently removes an instance from the server.
GETget_connection_state
Reports whether an instance is open, connecting or closed.
GETlist_instances
Lists every instance on the server with its connection status.
DELETElogout_instance
Logs the phone out of an instance while keeping the instance itself.

Message, 5 operations

POSTfind_messages
Queries the instance's stored messages, newest first, in pages.
POSTmark_message_as_read
Marks specific messages as read on the linked phone.
POSTsend_location
Sends a map pin with optional place name and address.
POSTsend_media
Sends a media message built from a public URL or base64 payload.
POSTsend_text
Sends a text message from an instance to a number or a group.

Group, 3 operations

POSTcreate_group
Creates a group and adds the given participants.
GETget_group_participants
Lists a group's participants and which of them are administrators.
POSTupdate_group_participant
Adds, removes, promotes or demotes participants of a group in one call.

Webhook, 2 operations

GETget_webhook
Reads back an instance's webhook URL, enabled flag and event list.
POSTset_webhook
Points an instance's events at a webhook URL and selects which events are sent.

Chat, 1 operation

POSTfind_chats
Queries the instance's stored chats with a filter, a limit and an offset.

Contact, 1 operation

POSTfind_contacts
Queries the instance's stored contacts with a filter and page controls.

Number, 1 operation

POSTcheck_whatsapp_numbers
Tells you which of a list of phone numbers actually have WhatsApp.

Use Evolution API from Claude Code, Cursor or Codex

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

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

Evolution API integration FAQ

What can you do with the Evolution API integration?: LiveContext exposes 19 operations on Evolution API, covering instance, message, group and webhook. Common uses include sending a delivery address to a driver, delivering an invoice PDF over WhatsApp and moving an instance to a different phone number.