Helpdesk
Tidio
Connect Tidio once and hand every teammate a governed MCP endpoint with 30 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards ship on the Black plan.
Automations
Put Tidio work on a schedule.
A trigger starts a sequence of steps: call a Tidio tool, transform the result, branch, wait, and ask a person when it matters.
Tidio digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch contacts
Tidio
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Tidio
Queued
Collections and dashboards
Report on Tidio without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Tidio health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Tickets
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
AI tools
Tidio tools for your AI agents
30 tools are ready to call through Elaichi's MCP endpoint the moment you connect Tidio, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
list_all_tidio_contacts
List Tidio contacts with all their properties. Returns: id, distinct_id, first_name, last_name, email, phone, language, country, city, created_at, email_consent, properties. Supports filtering by email address.
create_a_tidio_contact
Create a new Tidio contact. Returns: id. Required: distinct_id. At least one of email, first_name, last_name, or phone must also be provided.
get_single_tidio_contact_by_id
Get a single Tidio contact by id. Returns: id, distinct_id, first_name, last_name, email, phone, language, country, city, created_at, email_consent, properties. Required: id.
update_a_tidio_contact_by_id
Update a Tidio contact's properties such as email, phone, name, newsletter consent, and custom properties. Returns an empty 204 response on success. Required: id.
delete_a_tidio_contact_by_id
Delete a Tidio contact by id. Once deleted, the contact cannot be recovered. Returns an empty 204 response on success. Required: id.
tidio_contacts_bulk_create
Create up to 100 Tidio contacts in a single batch request using an all-or-nothing strategy. Returns: id, distinct_id, first_name, last_name, email, phone, language, country, city, created_at, email_consent, properties. Required: contacts array (each with distinct_id). At least one of email, first_name, last_name, or phone per contact.
tidio_contacts_bulk_update
Update up to 100 Tidio contacts in a single batch request using an all-or-nothing strategy. Returns an empty 204 response on success. Required: contacts array (each with id). Settable: email, first_name, last_name, phone, distinct_id, email_consent, properties. Maximum 100 contacts per request.
list_all_tidio_contact_properties
List all contact property definitions configured in the Tidio panel. Returns: name, label, type.
list_all_tidio_operators
List all Tidio operators — chat agents who interact with customers or website visitors in real-time — with all their properties. Returns: id, active, email, name, role, picture, last_seen.
list_all_tidio_departments
List all departments in Tidio. Departments are teams or groups of operators that handle specific types of customer inquiries or problems. Returns: id, name. The department id is a UUID used when assigning tickets via assigned_department_id.
list_all_tidio_tickets
List all Tidio tickets with their details but without messages. Returns: id, link, status, subject, priority, contact_id, contact_email, assigned_operator_id, assigned_department_id, custom_channel_id.
get_single_tidio_ticket_by_id
Get a single Tidio ticket by id with all details and messages. Returns: id, link, subject, contact_id, contact_email, priority, status, assigned_operator_id, assigned_department_id, custom_channel_id, messages. Required: id.
update_a_tidio_ticket_by_id
Update a specific Tidio ticket by id to change its status, priority, assignment, tags, or custom fields. Returns an empty 204 response on success. Required: id.
delete_a_tidio_ticket_by_id
Delete a specific Tidio ticket by id. Returns an empty 204 response on success. Required: id.
tidio_tickets_reply
Add a reply message to an existing Tidio ticket, either from an operator or a contact. Returns: id. Required: ticket_id, author_type, content.
create_a_tidio_ticket
Create a Tidio ticket on behalf of a contact. Returns: id. Required: contact_email, subject, message_content.
tidio_lyro_answer_ticket
Ask the Tidio Lyro AI agent to generate an answer for a ticket based on the provided ticket data. Returns: message_content. Required: ticket_id, subject, contact_email, contact_name, recipient_email, messages. Responding can take up to 40 seconds and currently only works for the first message in a ticket.
tidio_lyro_data_sources_upsert_website
Upload or update a website data source for the Tidio Lyro AI Agent. If a data source with the same URL already exists it is updated; otherwise a new one is created. Returns: id. Required: url, content, title.
tidio_lyro_data_sources_scrape_website
Submit a website URL to be scraped and used as a knowledge data source for the Tidio Lyro AI Agent. Each URL must be unique per project. Returns: id. Required: url.
list_all_tidio_lyro_data_sources
List data sources for the Tidio Lyro AI Agent, organized in a two-level hierarchy of folder and qa kinds. Returns: id, parent_id, title, type, kind, origin, status, used_by_lyro, used_by_copilot, sync_status, source_url, content, skip_auto_sync, manual_sync_available_at, next_auto_sync_at, created_at, updated_at.
create_a_tidio_lyro_data_source
Create a QA data source for the Tidio Lyro AI Agent. The content is provided as text and processed by the AI Agent. Returns: id. Required: title, content.
update_a_tidio_lyro_data_source_by_id
Update an existing QA data source for the Tidio Lyro AI Agent by id. Returns: id. Required: id, title, content.
delete_a_tidio_product_by_id
Permanently delete a product from Tidio Lyro AI recommendations by id. Deletion is irreversible and processed asynchronously. Returns an empty 202 Accepted response indicating the deletion has been queued. Required: id.
tidio_products_bulk_upsert
Bulk upload or update products for Tidio Lyro AI recommendations using batch processing. Products are processed in an all-or-nothing manner with a maximum of 100 products per request. Returns an empty 204 response on success. Required: products.
list_all_tidio_project
Get information about the authenticated Tidio project. Returns: project_id, status.
list_all_tidio_contact_viewed_pages
List pages a contact has viewed on your website in Tidio. Returns: url, viewed_at. Required: contact_id. Results cover the past 30 days.
list_all_tidio_contact_messages
List messages in a Tidio contact's conversation, including messages from the contact, chat operators, and chatbots. Returns: id, author_type, author_id, message, created_at. Required: contact_id.
create_a_tidio_contact_message
Send a message to a Tidio contact's conversation, attributed to the contact as if they sent it. Processing is asynchronous (202 Accepted). Returns: status. Required: contact_id, message. Message text must be 1–5000 characters.
list_all_tidio_ticket_tags
List Tidio ticket tags for the authenticated project. Returns a flat list of {id, name} objects sorted alphabetically by name.
list_all_tidio_ticket_custom_fields
List all ticket custom field definitions configured for the authenticated Tidio project. Returns: id, name, type, is_required, is_dynamic, values.
No tools match your search.
How it works
From Tidio account to governed MCP endpoint
Connect
Link a Tidio account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Tidio tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.