# Tidio Integrations: Channels, Zapier, API and Plan Gates (2026)

> How to connect Tidio: email, Messenger, Instagram, WhatsApp, native CRM and email apps on every plan, one-way Zapier, and API and webhooks from Plus.

_Source: https://professionalstoolkit.com/articles/tidio-integrations — The Professional's Toolkit · updated November 2026_

---

Tidio connects in three layers, and the plan decides which ones you get. Every plan, Free included, carries the channels (email, Messenger, Instagram, WhatsApp) plus the native app integrations: HubSpot, Salesforce, Zoho CRM, Klaviyo, Mailchimp, Shopify, WooCommerce, GA4 and Zapier among them. Slack and Stripe, the OpenAPI, webhooks and the Analytics API wait for Plus. Tidio sells Plus through sales, from $300 a month plus monthly usage [1]. Our verdict is simple. A small team can wire up its CRM, email list and store without paying for integrations. Code and two-way automation mean Plus.


**1,000** — Free outgoing WhatsApp messages per number a month on every Tidio plan; paid plans pay Meta's rates beyond that.



- **Every plan** — Channels, native apps and Zapier, Free included
- **Plus+** — OpenAPI, webhooks, Analytics API, Slack, Stripe
- **60 / 120** — OpenAPI requests a minute on Plus / Premium


## Connect the channels first: email, Messenger, Instagram, WhatsApp

Channels carry no Tidio fee on any plan (WhatsApp has its own Meta usage meter, below), and every user on the project can answer on all of them at once. **Email** connects three ways: forwarding from an existing mailbox at any provider, a new address on Tidio's own domain, or a one-click Gmail option that needs no forwarding setup. You can add several mailboxes and send from your own verified domain. One detail catches people when they disconnect: with forwarding, deleting the mailbox in Tidio is not enough, because the forwarding rule in Gmail must also go.

Messenger connects through a Facebook login and can pull in several Pages, inside Meta's 7-day reply window. Instagram needs a Business account linked to a Facebook Page; creator accounts are not supported. It brings in DMs, story replies and mentions, and top-level comments on Facebook and Instagram posts become tickets. Satisfaction surveys, seen status and forms stay on the website widget only. If the widget itself is not live yet, start with [our install guide](/articles/tidio-website-install).

### WhatsApp has its own rules and its own meter

The WhatsApp integration is free, and each number gets **1,000 free outgoing messages a month**, counting agent, Lyro and Flows replies alike [2]. Past that, paid-plan projects are billed by Tidio at month end at Meta's local rate for their country, with no Tidio markup, and can set a spending cap. Free and trial projects simply stop at 1,000. Replies are free only within 24 hours of the customer's last message. After that you need Meta-approved templates, which require Growth, Plus or Premium and are charged by Meta per category and country.

Outreach is not on the menu. Tidio cannot start a WhatsApp conversation, and templates go only into existing threads, never to a new contact. Calls, statuses, reactions and groups are not supported, and only 3 Flow triggers work on WhatsApp. You need Facebook Business Manager and a company number that can receive a call or text. A WhatsApp Business Account holds 2 numbers by default, normally up to 5 once Meta verifies the business.


> ⚠ **Templates need Growth or above:** After 24 hours without a customer message, WhatsApp only allows Meta-approved templates, which need Tidio Growth, Plus or Premium and are charged by Meta per category and country.


## The native integrations every plan gets, and what each syncs

Tidio says it offers 120+ integrations, but many directory entries are custom work built for Plus and Premium customers, not self-serve apps. The self-serve list on every plan covers CRMs, email marketing, store platforms, analytics and site builders such as WordPress, Wix and Squarespace. The details differ more than the logos suggest. Read the sync rules first. The table shows the ones readers ask about most.

| Integration | What it does |
|---|---|
| HubSpot | Creates or updates contacts; solved chat saved as a note; about 1 minute |
| Salesforce | Contacts plus transcript on solve; production or sandbox org |
| Zoho CRM | Auto contact sync and transcript notes; up to 5 minutes |
| Pipedrive, Zendesk Sell | Manual: agents create records from a chat |
| Klaviyo | Adds subscribers to one list; double opt-in by default |
| Mailchimp | Adds subscribers to one audience only |
| Omnisend | Adds subscribers; no double opt-in |
| GA4 | Widget, chat, Flow and lead events; up to 48 hours to appear |
| Shopify | Order history, customer import, Flows for carts; Lyro product recommendations need a paid Lyro quota |

Watch the field rules. The CRM syncs carry email, name and phone, plus properties you map yourself. When Tidio has a blank value, HubSpot and Salesforce keep their own data, but an empty mapped field can overwrite data in Zoho CRM. That difference matters if agents rarely fill in phone numbers. Klaviyo needs a private API key with full access to lists, profiles and subscriptions, and new subscribers appear only after they confirm by email unless you change the list setting. Contacts reach these tools through the pre-chat survey, a Flow that collects details, or an agent's edit during a chat.

Shopify is the deepest store integration. Native Shopify actions inside the inbox, such as editing orders, refunds and shipping addresses, start at Growth. After installing the Shopify app you switch the widget on under the theme's app embeds, and you repeat that each time you change themes. Forget it once and the chat disappears. WooCommerce runs through the Tidio plugin. Judge.me works only with Judge.me's own paid plan.


> 💡 **Test blank fields before syncing:** In Zoho CRM an empty mapped Tidio field can overwrite existing data, while HubSpot and Salesforce keep theirs. Map only fields agents reliably fill.


## Zapier is one-way, and only for Flow data

Zapier is free on Tidio's side and reaches any CRM Zapier supports, including those without a native Tidio app. The catch is direction. **Data moves only from Tidio to the other app** [3]. Zapier is not a tile in the integrations list. It is a Send to Zapier action inside the Flows editor, set up with an Integration Key, so the Zap fires only where a Flow reaches that step.

That shapes what reaches Zapier. Only data a Flow collects goes out; contact details an agent types by hand are not sent. Nothing comes back into Tidio this way, so a Zap cannot open a ticket or update a contact in your inbox. Tidio's help suggests Zapier as the route around the native Mailchimp double opt-in. For two-way work you need the OpenAPI and webhooks. That means Plus.

## Plus-only apps, Lyro Connect and the Zendesk token question

Slack (notifications and lead alerts) and Stripe (payment data and canceling subscriptions, with no payment processing) are listed for Plus and Premium only. Plus also brings Lyro Connect, which puts Lyro on top of a help desk you already run and creates a ticket there when it cannot answer; Tidio names Zendesk, Intercom and Salesforce. Custom integrations from the directory, such as Twilio or Telegram, are built by Tidio for Plus and Premium customers. Plan changes, seat caps and the separate usage meters are covered in [our pricing breakdown](/articles/tidio-pricing).

The Zendesk integration itself is on every plan. An agent creates a Zendesk ticket from a Tidio chat, with subject, priority, assignee, status and a transcript preview. It asks for a Zendesk API token, as does Lyro's import of Zendesk tickets. Zendesk's side has changed. Our Zendesk records say no account can create new API tokens since October 2026, and all Support API tokens stop in April 2027. Confirm the current connection method with Tidio before you build on it.

## The developer platform: OpenAPI, webhooks, Analytics API

**The full OpenAPI needs Plus or Premium.** One exception exists. Starter or Growth projects with a paid Lyro or Flows package can call the product endpoints that feed recommendations, at 10 requests a minute per project. Plus allows 60 requests a minute and Premium 120, and calls above the limit return HTTP 429 [4]. Owners or admins generate a client ID and client secret, sent as two headers, and every request must ask for version 1 in its Accept header.

The API covers contacts, tickets (create, reply, update, tags, custom fields), operators, the project, Lyro data sources, Lyro answering a ticket's first message, and products. Pagination uses cursors. Batch calls take up to 100 contacts or products, all or nothing, so one bad record fails the batch. Events you create through the API send no webhooks. Tidio's Terms let it set limits or end API access at any time.

Webhooks, also Plus and Premium, arrive as signed JSON with an HMAC-SHA256 signature. Events include contact created or updated, an operator reply and a chat solved by Lyro. Failed deliveries retry up to 9 times, from 5 seconds to 3 hours apart. A receiver slower than 4 seconds counts as a failure. Order is not guaranteed and duplicates happen. Deduplicate everything.

The Analytics API is read-only and uses the same credentials. It covers conversations, tickets, ratings, Lyro threads and Flows stats, loaded daily, with yesterday's data in by about 10:00 UTC. It allows 50 requests a second shared across users, with a 25-second query timeout. A read-only Analytics MCP server lets Claude Code, Claude Desktop, Cursor or ChatGPT Desktop query that data directly.


> 💡 **Build webhook receivers to deduplicate:** Tidio's webhooks (Plus and Premium) can arrive out of order or twice, and a reply slower than 4 seconds counts as a failed delivery. Acknowledge fast and process later.


## Widget SDK, Lyro Actions and MCP

Two developer tools do not wait for Plus. The widget SDK runs on every plan, though Tidio does not help implement it. It opens, closes, shows or hides the widget, tracks custom events, sets visitor data and contact properties, and listens for events such as a visitor message. Hiding the widget does not stop Flows from triggering. On stores other than Shopify, abandoned-cart tracking needs a developer to call the track method.

Lyro reaches outside systems through Actions, which call external APIs for order status, returns or bookings. Free, Starter and Growth get 1 Action, 3 with a paid Lyro quota, and Plus gets 10. Action templates for Calendly, Shopify order status and Klaviyo, Mailchimp or HubSpot contacts come with Plus and Premium; only some paid-Lyro subscribers get them. Lyro can also connect to external MCP servers, where an admin picks which tools it may use. The [AI playbook](/articles/tidio-ai-playbook) covers how to set those limits.


## FAQ

**Can Tidio send SMS or take phone calls?**

Not natively. SMS, voice and Telegram appear in Tidio's directory only as custom integrations Tidio builds for Plus and Premium customers, or as third-party integrations.

**Does Tidio work with Outlook email?**

Yes. Outlook or any other provider connects by forwarding to a Tidio address; Gmail also has a one-click option without forwarding.

**Can I connect more than one Facebook Page or mailbox?**

Yes. Messenger can pull in several Facebook Pages, and Tidio's ticketing accepts several mailboxes with your own verified sender domain, on every plan.

**Can I pull Tidio data into a BI tool without Plus?**

Not through the API. The Analytics API and its MCP server need Plus or Premium; on lower plans transcripts export one at a time as CSV.


## The bottom line

Tidio's integration story splits cleanly at Plus. Below it, a store or small team gets every channel, CRM contact sync, email-list capture, GA4 events, Shopify data and one-way Zapier at no integration charge, with WhatsApp messages past 1,000 billed at Meta's rates. Above it come Slack, Stripe, Lyro Connect, two-way automation through the OpenAPI and webhooks, and the Analytics API. Map your must-have connection to that line first. If it sits above, budget for Plus. If you run Zendesk, settle the token question with Tidio before anything else.



## Sources

[1] [Toggle state: initial, read from the US on 2026-11-04] This website uses cookies. We use — https://www.tidio.com/pricing/ (2026-11)
[2] Tidio help: Integration with WhatsApp — https://help.tidio.com/hc/en-us/articles/9392748807580-Integration-with-WhatsApp (2026-11)
[3] Tidio help: Integration with Zapier — https://help.tidio.com/hc/en-us/articles/5422427950236-Integration-with-Zapier (2026-11)
[4] Tidio API docs: Rate Limiting — https://developers.tidio.com/docs/openapi-rate-limiting (2026-11)
[5] Tidio help center — https://help.tidio.com/hc/en-us
[6] Tidio Terms of Service — https://www.tidio.com/terms/
[7] Tidio developer documentation — https://developers.tidio.com/

