Integration

Tidio integration

Tidio Open API, the public REST interface of the Tidio live chat and helpdesk. Manage contacts and their custom properties, read a contact's chat history and send a message into it on the contact's behalf, work the ticket queue (list, read, update status, priority, assignment, tags and custom fields, reply publicly or internally, create a ticket as a contact, delete), and read the supporting directories of operators, departments and ticket tags. Authentication uses an OpenAPI client id and client secret pair generated in the Tidio project settings. Every call must also carry Accept set to application/json; version=1, since a request without that version token is refused with 406 missing_api_version before the credentials are read.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

Common Tidio use cases

  • honouring a data erasure request
  • removing a ticket created by mistake
  • scanning the queue for unassigned tickets
  • routing a new ticket to the billing department
  • pushing a signup from your own system into Tidio
  • summarising a visitor's chat before escalating it
  • reading the whole ticket before drafting an answer
  • picking the operator to attribute a ticket reply to
  • marking a ticket solved and tagging it for reporting
  • reading a visitor's stored properties before answering

What you can do with Tidio

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.

Ticket, 6 operations

  • create_ticket_as_contactCreate ticket as contactPOSTOpens a ticket as if the customer had written in, addressed by email.
  • delete_ticketDelete ticketDELETEPermanently deletes a ticket.
  • get_ticketGet ticketGETReturns a single ticket including its message thread.
  • list_ticketsList ticketsGETLists tickets with status, priority and assignment.
  • reply_to_ticketReply to ticketPOSTReplies to a ticket as an operator or as the contact, publicly or internally.
  • update_ticketUpdate ticketPATCHChanges a ticket's status, priority, assignee, tags or custom fields.

Contact, 5 operations

  • create_contactCreate contactPOSTCreates a contact identified by your own distinct id.
  • delete_contactDelete contactDELETEPermanently deletes a contact and its history.
  • get_contactGet contactGETReturns a single contact with its custom properties.
  • list_contactsList contactsGETLists contacts page by page, or looks one up by email address.
  • update_contactUpdate contactPATCHUpdates selected fields of a contact, leaving the others untouched.

Message, 2 operations

  • list_contact_messagesList contact messagesGETReads a contact's chat messages with their author type.
  • send_contact_messageSend contact messagePOSTInjects a message into a contact's chat on the contact's behalf.

Department, 1 operation

  • list_departmentsList departmentsGETLists departments with their identifiers.

Operator, 1 operation

  • list_operatorsList operatorsGETLists operators with their role and last seen time.

Project, 1 operation

  • get_projectGet projectGETReports the project identifier and whether the chat is currently staffed.

Property, 1 operation

  • list_contact_propertiesList contact propertiesGETLists the custom contact properties with their names and types.

Tag, 1 operation

  • list_ticket_tagsList ticket tagsGETLists the ticket tags with their identifiers, sorted by name.

Use Tidio from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Tidio once

    Add your Tidio 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.

Tidio integration FAQ

What can you do with the Tidio integration?

LiveContext exposes 18 operations on Tidio, covering ticket, contact, message and department. Common uses include honouring a data erasure request, removing a ticket created by mistake and scanning the queue for unassigned tickets.

Popular integrations

Browse the whole catalog