Tidio Connector
Connector status: In progress Being built. Not verified yet.
Illustration · sample data
Sync example
Source
Tidio
Connector status: In progress
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Connector implementation
Build the Tidio integration
Live chat, chatbot, and ticketing solution for small and mid-size businesses
Implementation Overview
Implement a Tidio connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
developers.tidio.com/
| Property | Value |
|---|---|
| Integration surface | Docs |
| Status | In progress |
| Category | Messaging & Chatbots |
| Setup complexity | advanced |
| Vendor documentation | developers.tidio.com/ |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | Not recorded |
| MCP server | Not recorded |
| Last researched | 2026-04-12 |
Tidio calls its API ‘OpenAPI’ as a product name; no formal OAS file published.
Authentication
-
Keep developers.tidio.com/ linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Tickets, conversations, and support context
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
| Resource | Direction | Conflict handling |
|---|---|---|
contacts | bidirectional | source_wins, loop guard none |
Tidio is the record of its contacts; update_contact sets the named fields and converges, and the next full read carries the written values back unchanged.
Mapping To Tajo/Brevo
contacts → Brevo contact
Requires: workspace api key.
| Source field | Brevo destination | Via | Note |
|---|---|---|---|
email | email | — | |
firstName | attributes.FIRSTNAME | — | |
lastName | attributes.LASTNAME | — | |
id | attributes.TIDIO_ID | — |
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.