Tidio

This connector wraps the Tidio OpenAPI, Tidio's REST API at https://api.tidio.com (docs: https://developers.tidio.com). Tidio has no GraphQL API.

Plan: the OpenAPI is available on the Plus and Premium plans only (Starter, Growth and paid Lyro plans reach just the product-recommendation endpoints, which this connector does not use). Free has no API access.

Setup:

1. In the Tidio panel open Settings → Developer → OpenAPI (https://www.tidio.com/panel/settings/developer). Only the project owner and admins see this section.
2. Click Generate API Key: Tidio shows a pair of keys once — copy both.
3. Paste the key starting with ci_ into TIDIO_CLIENT_ID and the one starting with cs_ into TIDIO_CLIENT_SECRET.

Authentication: every request carries X-Tidio-Openapi-Client-Id and X-Tidio-Openapi-Client-Secret, plus the mandatory version header Accept: application/json; version=1. The connector sends all three.

Workflow:

• Contacts: tidio_list_contacts, tidio_get_contact_by_email, tidio_get_contact, then tidio_get_contact_messages for the chat history with that contact, or tidio_update_contact to change name, email, phone or custom properties.
• Tickets (helpdesk): tidio_list_tickets → tidio_get_ticket (with messages) → tidio_reply_to_ticket. Replying as an operator needs an operator ID from tidio_list_operators.

Live chats are read through the contact: the OpenAPI has no endpoint to list conversations or to send a chat message as an operator; the chat history is tidio_get_contact_messages, and written replies go to tickets.

Contact properties: tidio_update_contact only accepts properties already defined in the Tidio panel (Settings → Contact properties); an unknown property or a wrong type is answered with a validation error. A field set to null is cleared; a field left out stays untouched.

Pagination: list tools answer with meta.cursor; pass it back as cursor for the next page. A null cursor means the last page.

Rate limits (per project): Plus 60 requests/minute, Premium 120/minute. A 429 answers too_many_requests; x-ratelimit-remaining shows what is left.

Errors come as { "errors": [{ "code", "message" }] } — not_found, not_valid, too_many_requests, …

Out of scope here: Lyro data sources and products, webhooks, the Analytics API.