What we do
Tools
Industries
Department
How we workLet's talk →
Home/Tidio/Tidio Integrations That Stop at the Email
Tidio

Tidio Integrations: What Reaches Klaviyo, HubSpot, Slack and Your Store

A shopper asks in chat when the navy jacket is back in medium, leaves an email, and turns up in Klaviyo as an address on a list with nothing about the jacket. That's how Tidio's Klaviyo integration is built: it passes the email. Every Tidio integration carries its own slice of a conversation, and a few, including Slack, webhooks and the OpenAPI, only come with the Plus and Premium plans.

Tidio integrations and the data each one carries

Most are installed from Integrations in the left sidebar of the Tidio panel.

Integration What it carries The catch
Shopify Shopping history and active carts in the inbox. Agents can send products into the chat, and cancel orders, refund or change a shipping address from the dashboard. Lyro's Shopify templates run on the same connection. Orders handled outside Shopify, by a second store or a 3PL, aren't in it.
WordPress and WooCommerce WordPress is listed as a website-builder integration for adding the widget, and Tidio's help documents sending WooCommerce products to a customer from the chat. Check how much WooCommerce order detail your agents actually see before you plan support around it.
Klaviyo The email address, into one Klaviyo list, from a pre-chat survey with newsletter consent, a contact you mark Subscribed, or a flow's Subscribe for Mailing node. One list per integration, and the newsletter question in the pre-chat survey stays on while it's connected. On a double opt-in list, people appear only after confirming.
Mailchimp, MailerLite, Brevo, Omnisend, ActiveCampaign Each has its own Tidio integration for adding chat contacts to email marketing. Read each one's article for the fields that go across before building a segment on chat data.
HubSpot Contacts created or updated in Tidio are created or updated in HubSpot, with custom properties you map in setup. Each solved conversation is saved as a note on the contact. Only solved conversations become notes. Solving them automatically through Workflows needs the Growth plan or higher.
Salesforce, Pipedrive, Zoho CRM, Zendesk Each has a Tidio integration article for sending chat contacts and conversations across. Coverage differs by app, so map the fields you rely on before switching one on.
Slack Chat and lead alerts in the channels you choose, with rules for which conversations go where. Someone can spot a chat in Slack and assign it in Tidio. Plus and Premium only.
Zapier A flow's Send to Zapier node fires the Contact Sent From Bot trigger, which a Zap can pass to almost any app. Only what the flow collected goes across. Anything an agent typed into Tidio by hand stays behind.
WhatsApp, Messenger, Instagram Messages from each channel land in the Tidio inbox. WhatsApp messages you start, rather than replies, go through WhatsApp message templates.
OpenAPI and webhooks Contacts, conversations, tickets and Lyro data sources through the API. Webhooks for events such as a new contact, a conversation solved by Lyro or an operator, a new ticket or a satisfaction rating. Plus and Premium only, apart from Lyro product endpoints on a paid Lyro quota.

Chat data that never lands where you expected

The Klaviyo profile has an email and nothing else

How you'll know: Shoppers who asked about sizing or a restock sit in one list with no record of what they asked.

Fix: On Plus or Premium, a webhook on each solved conversation can carry the topic and product into Klaviyo as profile properties through Klaviyo's own API. No Tidio setting does this; it has to be written.

The Zap runs, but half the fields are blank

How you'll know: A Zap from Send to Zapier passes the name, but not the order number an agent added later in the chat.

Fix: Ask for the field inside the flow itself, or move the job to webhooks and the OpenAPI, which read the contact as it stands.

The Slack tile asks for an upgrade

How you'll know: You're on a plan below Plus and want new leads in a team channel.

Fix: Webhooks and the OpenAPI are on the same plans as Slack, so a custom build can't stand in. A Send to Zapier node at the end of a lead flow can post to Slack through Zapier; Tidio's help doesn't name a plan for that node, so test it on yours.

HubSpot never hears about chats nobody solved

How you'll know: Open conversations don't show up as notes on the contact, so sales misses them.

Fix: Make solving part of closing a chat, or solve automatically through Workflows on Growth or higher.

Tidio connections, plan by plan

Does Tidio integrate with Shopify and WooCommerce?

Yes. The Shopify integration shows a shopper's purchase history and carts in the inbox, lets agents send products, cancel orders, refund and change shipping addresses, and feeds Lyro's Shopify templates. For WooCommerce, Tidio's help documents sending products to customers straight from the chat, and WordPress is listed as an integration for putting the widget on the site.

Is Tidio's Slack integration available on every plan?

No, only on Plus and Premium. Tidio's webhooks and most OpenAPI endpoints sit on the same two plans, so a custom build can't replace Slack on a lower one. A flow that ends in Send to Zapier is the route worth testing there.

Does Tidio integrate with Klaviyo and Mailchimp?

Yes, both have Tidio integrations. The Klaviyo one sends the email address into a single list, from a pre-chat survey with newsletter consent, a contact you mark Subscribed, or a flow's Subscribe for Mailing node. Read Mailchimp's article for its fields before planning segments around it.

Does Tidio have an API?

Yes, in three parts. The OpenAPI reads and writes contacts, conversations and tickets and manages Lyro's data sources. Webhooks send events such as contact.created, conversation.solved_by_lyro and ticket.created to your endpoint, set up under Settings, Developer, Webhooks. Both need Plus or Premium. The widget's JavaScript SDK sets contact properties and listens for chat events in the browser.

Who builds the Tidio connections its own integrations leave out?

n-frames builds them on Tidio's webhooks, OpenAPI and widget SDK: chat topics and products carried into Klaviyo or your CRM, store and subscription facts set as contact properties, and solved conversations turned into the next step in your order or support system.

Store and subscription facts Tidio has no field for

Tidio holds what happens in the chat. A loyalty tier, the next renewal date or a wholesale flag lives somewhere else. Contact properties are where those belong: define the property under Settings, Contact Properties, then set it from the widget's JavaScript with setContactProperties once the chat code has loaded, or through the OpenAPI on Plus and Premium.

n-frames builds that feed from your store, subscription app or billing system, and the webhook receiver that takes a solved conversation or a new ticket and writes what it learned into your CRM, email platform or order system. When the question is one Lyro should answer from live data, that's covered on Tidio AI and Lyro Actions.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.