LiveChat Integrations: Shopify, CRMs and the Marketplace in Text

LiveChat, now sold to new customers as Text plans, connects to stores and CRMs with no separate integration fee on any Text plan, whether the link is a ready-made app or a custom API connection; the partner tool's own subscription still applies.^[1] The answer splits in two. Text, which every new sign-up gets, offers ready-made apps for Shopify, WordPress with WooCommerce, and Webflow; API connections for BigCommerce, Adobe Commerce and other platforms, mapped by a Text solutions engineer; and CRM and marketing actions built as Skills in Playbook. The Text Marketplace lists third-party apps by product, and some of them, such as Zendesk, Pipedrive and Zapier, are built for the LiveChat app that existing customers keep. Know which side you are on first.

Text or the LiveChat app: who owns which integration

Most confusion about LiveChat integrations comes from two products sharing one brand. Help pages under livechat.com/help describe the LiveChat app, so a tutorial found there may not apply to Text at all. Text features are not added to legacy LiveChat plans, and a Text account is a separate workspace: opening one does not move a LiveChat plan or its conversation history. The table sorts the named integrations by where they live and how they connect.

For a new buyer, the first six rows come with the Text plan itself, with no integration line from Text on the invoice, though the CRM, email or store platform keeps its own subscription. The cost that does grow is seats: Text Essential starts at $19 per user per month billed annually, or $25 per user per month billed monthly, and every user who answers chats or tickets needs one. That annual rate assumes a direct sign-up; Shopify App Store installs are billed differently, as the Shopify section explains. Plan details and break-even points are in our LiveChat pricing guide. The last row is different. It needs a LiveChat account.

Connecting a store: Shopify, WooCommerce and Webflow

Shopify

Text is listed in the Shopify App Store as its own app, reviewed by Shopify, and installs in three steps with no code or theme editing. On every Text plan and every Shopify plan, the widget runs on the storefront and the Thank You page, while chat on the checkout page itself needs Shopify Plus, a restriction Shopify sets.^[2] Once connected, agents see each visitor's live cart, past orders and lifetime spend inside Text, and get notified when items are added, removed or ordered mid-conversation. One Text account can run several Shopify stores.

The install route changes how you are billed. Installing from the Shopify App Store bills Text through Shopify every 30 days as an app charge, and Text says signing up directly makes annual billing cheaper. Stores with a custom or headless Shopify storefront should skip the standard app and use the Sales Tracking API instead. Shopify order data that feeds Text's sales reports syncs once a day. These reports are not a live feed.

WordPress and WooCommerce

WooCommerce connects through the WordPress plugin AI Chatbot by Text, live for WooCommerce stores since July 2026. The install path is Plugins, Add New, Install, Activate, then Connect to Text, and it needs WordPress 6.0 or higher and PHP 7.4 or higher, with no developer, API key or theme edit. The plugin is free to download but needs a Text trial or paid plan. With WooCommerce active, Text shows the visitor's cart live to the team and the AI Agent, plus total spent and total orders. Without WooCommerce, the widget still works but carries no store data.

Webflow

In Text, open Settings, then Website widgets, click Add to Webflow and authorize; the app asks to read and write custom code and site data, including publishing. Publish the site first. The status flips to Connected only after widget activity on the live site. Text sets no limit on connected Webflow sites, and colors, position, greeting and launcher style are edited in Text, not in the Webflow Designer.

Stores that connect through the API

BigCommerce, Adobe Commerce, Magento, Salesforce Commerce Cloud, SAP Commerce Cloud, commercetools, Medusa and Swell have no plugin. A Text solutions engineer maps catalog, cart and order data into the chat layer through each platform's own API. That is why the same connection works on a default storefront and on a fully headless build. Text is priced per Text plan, separate from the store platform, whose subscription stays unchanged. Expect a scoping call.

Two building blocks matter if your platform appears on no list at all. Product recommendations can come from a catalog sent through the Product Directory API or a Google Shopping XML feed re-synced hourly, and the Recommend products skill is live on every Text plan. Sales tracking works on any stack through one API call on the order confirmation page, or through Google Tag Manager if a container is already installed. For orders from November 2026, the sales attribution window is 7 days; earlier orders keep the 30-day window and are not recalculated. Both paths are covered in our LiveChat for ecommerce guide.

CRMs, email marketing and Slack through Playbook skills

In Text, CRM and marketing integrations are not separate apps. They are actions and triggers inside Skills, the no-code automations in the Playbook section, and one skill can mix several of them with webhooks that call any HTTP endpoint. A CRM connection does not sync every field on its own: you pick the trigger, configure each action and test the result. Nothing runs until you build it.

Salesforce

Salesforce is connected once from an automation action, with no plugin and no change in Salesforce Setup. It needs an active Salesforce account plus permission to configure skills in Text and to create records in Salesforce. Skills can create, update and look up leads, contacts and accounts by record ID or email; cases can be created and updated but not looked up the same way. To avoid duplicates, run Find contact by email or Find lead by email before any create step. For volume, Queue actions batch records into a Salesforce Bulk API job.

HubSpot, Klaviyo, Mailchimp and Slack

HubSpot connects through a simple authorization with no developer, and it can also start a skill when a contact is created or deleted. Two rules trip people up: a skill must be published before it runs, and any customer detail a step depends on must be collected earlier in the same skill. Klaviyo gets five skills (get profile, create or update profile, track event, subscribe, unsubscribe), each needing a connected Klaviyo credential and a customer email in the conversation. Mailchimp adds leads to an audience. Text itself does not send campaigns. Slack actions cover thread replies, ephemeral messages and direct messages, plus a reaction trigger.

Text also publishes code guides for Salesforce chat routing and HubSpot sync, and marks both as not production ready. The routing sample needs a Text account on Growth or higher, and the sync sample can lose a sync on restart and create duplicate notes on repeated webhooks. Treat them as starting code for a developer. Text plans include 10,000 API calls a month on Essential and 20,000 on Growth, and on either plan each extra pack of up to 100,000 calls costs $29.50 a month.

Analytics and AI assistants

Text has no native Google Analytics integration.^[3] To get chat events into GA4, you build a Playbook skill with a webhook step that sends them. Plan it as a small build. It is not a setting. For AI assistants, Text offers a ChatGPT plugin, live for every account since August 2026 and connected per teammate with that teammate's permissions. The MCP server at mcp.text.com gives assistants access to tickets and chat transcripts under the connected user's permissions on every Text plan, with setup guides for Claude Desktop, Claude Code, Claude Web and ChatGPT. Neither replaces a CRM sync.

Existing LiveChat customers: the Marketplace apps you keep

Existing LiveChat customers keep their plan, their price and the Marketplace apps installed in the LiveChat app. The Marketplace itself is the Text Marketplace, filterable by product (Text, LiveChat, HelpDesk, ChatBot), and the vendor puts it at 200+ apps. Among the apps built for the LiveChat app, the Zendesk app creates Zendesk tickets from chats, forwards offline messages as tickets and shows the visitor's ticket history when the email matches. The Pipedrive app adds contacts and attaches transcripts to Persons and Deals, though a transcript can join only a Deal that already exists. LiveChat also works as a trigger app in Zapier, and Microsoft Teams, translator, SnapCall and Telegram apps serve the LiveChat app too.

Read the fine print before relying on any Marketplace app. Some are built by third parties and carry their own fees set by their developers.^[4] Under Text's Terms, Marketplace apps are not part of the Services, and the Verified badge marks a usability review only, not a guarantee. A LiveChat customer who wants Text's AI Agent, shared inbox or ticketing has to move to Text, and can run a Text trial side by side first. Updating the mobile app does not add those features. For developer-built connections, see our LiveChat API guide.

The bottom line

For a new buyer, LiveChat integrations now mean Text integrations, and they come down to three checks. If your store runs on Shopify, WooCommerce or Webflow, the connection is a ready-made app with no separate fee from Text; on BigCommerce, Adobe Commerce or a headless build, it is an API mapping that a Text solutions engineer sets up. CRM, email and Slack connections are Playbook skills you configure and test yourself, and analytics needs a webhook skill. Apps built for the LiveChat app, such as Zendesk and Pipedrive, matter only to existing LiveChat customers, and any Marketplace app can carry third-party fees.