Your tools.Working together.

WordPress

Install chat and turn approved public site content into reusable answers.

WooCommerce

Help shoppers understand the catalog and check an order through a separate identity-verified lookup.

Shopify

Connect store knowledge to AI and handle supported order questions with verification, while your team keeps the conversation in Inbox.

Wix

Add Message chat to your Wix site, then review the public pages you want AI to use.

Webflow

Add Message chat to the published Webflow site and approve the public content behind its AI answers.

Squarespace

Keep visitors in a conversation while your team handles the request from the shared Inbox.

BigCommerce

Connect the storefront chat and supported store sources, then check your chosen catalog scope before syncing.

Magento

Bring public catalog and store knowledge into Message AI, with a separate verified lookup for order status.

Joomla

Install the Message Joomla plugin to bring approved public website content into your customer-support knowledge workflow.

Drupal

Connect published Drupal content to Message knowledge through the native module or a configured public JSON:API source.

PrestaShop

Connect approved public store knowledge and a separate verified order-status lookup with the Message PrestaShop module.

Use the Message OpenCart extension for public store knowledge and verified order-status questions, starting with the supported default-store setup.

Framer

Add Message live chat to a Framer website using the widget embed, then connect approved public pages to your support knowledge.

Use the Message widget on your Weebly site for customer conversations, with public website knowledge configured separately from private store data.

Embed Message live chat on a Duda site and route visitors into the correct support workspace, especially when an agency manages several sites.

Carrd

Add Message live chat to a Carrd landing page through a supported custom-code embed, with site knowledge reviewed separately for AI answers.

Bring storefront questions and verified Ecwid order context together in a planned Message connector.

Shopware

Plan a Shopware connection for approved catalog knowledge and verified order questions, scoped to the right sales channel.

Ghost

Use published public Ghost posts and pages as reviewed Message AI knowledge, keeping member-only content outside the public feed.

Contentful

Connect selected Contentful entries to Message knowledge using the published delivery path and an explicit space, environment and field mapping.

Strapi

Connect a selected Strapi collection to Message knowledge with explicit fields and a token limited to the content needed for customer answers.

Sanity

Connect a selected Sanity dataset and document type to Message knowledge, using published content and an explicit field mapping.

Storyblok

Bring selected published Storyblok content into Message knowledge, with the region and content fields configured for your support material.

Prismic

Read selected published Prismic content into Message knowledge, with repository, content type and fields chosen for customer-facing answers.

GitHub documentation

Use selected Markdown and text files from a public GitHub repository as reviewed Message AI knowledge, with explicit paths instead of a whole-repository crawl.

Zendesk Help Center

Connect published public Zendesk Help Center articles as Message knowledge. Moving ticket history is a separate migration workflow.

Google Drive & Docs

Select Google Docs or supported text files, preview the content and approve it for the site’s knowledge.

Google Sheets

Select the spreadsheet data that should become knowledge instead of importing an entire workbook indiscriminately.

Notion

Plan your Notion integration with Message. Design a Notion-to-Message knowledge feed that publishes only the pages your team has approved for customers.

Confluence

Plan a Confluence knowledge connection that selects useful support pages while keeping internal spaces and restricted notes private.

Dropbox

Plan a Dropbox connection for approved support documents, with folder selection and private-file boundaries defined before ingestion.

Box

Plan a Box knowledge connector for selected customer-support files, with clear ownership, access checks and approval before AI use.

SharePoint

Plan a SharePoint knowledge connection for selected support libraries. Keep internal sites and customer-facing knowledge separate.

OneDrive

Plan a OneDrive connection that brings selected, approved documents into Message knowledge without importing an employee’s entire drive.

Airtable

Plan an Airtable connector for selected tables and fields, separating public product knowledge from private customer records.

Facebook Messenger

Bring eligible Page messages into the same queue as chat, email and calls. Assign and reply from the customer conversation.

Instagram

Turn eligible Instagram business messages into conversations your team can own and answer in Inbox.

WhatsApp Business

Handle eligible WhatsApp Business conversations alongside website chats, with source labels and a clear owner.

Telegram

Use supported private-bot or business conversations as another entry point into the shared Inbox.

Discord

Bring the selected Discord support channel into Inbox so a question can be assigned and answered by your team.

Gmail

Receive customer email in Inbox and send text replies through the connected Gmail mailbox.

Outlook

Bring Outlook email into Inbox and answer through the connected mailbox beside other customer requests.

LINE

Explore the planned LINE messaging connector: incoming customer messages, agent replies and source filters in one support workspace.

Viber

Review the proposed Viber connector for Message Inbox, including account eligibility, customer identity and reliable reply handling.

WeChat

Plan a WeChat connection with account type, region and permitted messaging workflows established before adding it to Message Inbox.

HubSpot

Company, lifecycle stage and lead status give the agent a starting point before asking the customer to repeat their history.

Salesforce

Read the matching Salesforce Contact and Account name beside the conversation, then continue account work in Salesforce.

Find the matching person, their organization and owner before passing a sales or support request to the right colleague.

Microsoft Dynamics 365

See the matching Dataverse Contact and job title without navigating away from the customer request.

Zoho CRM

Read the matching Contact’s account, title and email opt-out status without opening another search.

Plan read-only Freshsales customer context in Message, with matched contacts, account ownership and relevant deal information.

Plan a Copper connector that gives support staff selected relationship and opportunity context without exposing private CRM notes.

Plan a read-only Close connection for lead relationships, assigned owners and relevant opportunity context alongside support conversations.

Plan an Insightly connector that helps agents understand a customer’s organization and ownership without copying the whole CRM.

Plan a monday CRM connector with selected boards and columns, so support sees useful account context instead of every internal update.

Plan a Keap integration that helps support understand confirmed contacts and relevant relationship details without starting campaigns.

Plan a SugarCRM connector for selected account and contact context, with explicit module mapping and employee-only access.

Plan an Attio connector for selected people, companies and custom attributes, with clear boundaries between relationship context and AI knowledge.

Mailchimp

Check the selected audience member’s subscription status and tags before investigating a missing marketing email.

Read the matching profile and marketing consent before investigating campaign questions.

ActiveCampaign

Read matching contact details and hard and soft bounce counts inside Inbox.

Brevo

Email and SMS block status help an agent investigate delivery questions without overriding consent.

SendGrid

Confirm whether the exact email is present as a Marketing Contact. Keep the customer conversation open while you investigate in SendGrid.

Resend

Look up the contact and subscription status to help explain missing emails without changing the customer’s preferences.

Kit

Plan your Kit (formerly ConvertKit) integration with Message. Plan a custom Kit workflow around explicit subscriber consent. A support conversation should never silently become a marketing subscription.

Plan a MailerLite connector for selected subscriber context, helping support understand email issues while preserving consent.

Plan a Constant Contact connection to help agents investigate subscription questions without changing customer marketing preferences.

Plan an Omnisend connector for useful subscriber context across email and SMS, with channel-specific consent kept intact.

Stripe

See matching customer records and recent payments and invoices. Disputed payments help the agent spot an issue that needs a careful response.

QuickBooks Online

Find the matching customer’s active status, open balance and currency. Give billing support a starting point while invoices remain in QuickBooks.

PayPal

Plan your PayPal integration with Message. Design a read-only PayPal support workflow around a verified transaction. Keep payment controls with the people who are authorized to use them.

Square

Plan your Square integration with Message. Design a read-only Square support workflow around a verified transaction. Keep payment controls with the people who are authorized to use them.

Xero

Plan a read-only Xero connector for selected invoice and payment context, keeping accounting records separate from public AI knowledge.

Plan a Chargebee connection for subscription and invoice context, helping agents understand billing questions before taking action.

Paddle

Plan a Paddle connector for selected customer, transaction and subscription context without exposing billing records through public search.

Plan a Recurly connector that helps agents understand account, subscription and invoice questions while leaving billing changes controlled.

Slack

Deliver supported AI-help requests and outcome notifications to the team’s Slack destination.

Microsoft Teams

Send supported AI-help requests and outcome notifications to the selected Microsoft Teams destination.

Linear

Plan your Linear integration with Message. Plan a Linear handoff with the support reference, an approved summary and an owner. Keep the customer conversation in Message.

Jira

Plan your Jira integration with Message. Plan a Jira handoff with the support reference, an approved summary and an owner. Keep the customer conversation in Message.

Asana

Plan an Asana connection for deliberate customer follow-up tasks, with conversation references and clear assignment boundaries.

Trello

Plan a Trello connection that turns an approved follow-up into a card with the customer conversation linked for context.

ClickUp

Plan a ClickUp integration for assigned support follow-ups, using selected lists and explicit status mapping.

Basecamp

Plan a Basecamp connector for selected project to-dos, keeping customer requests attached to the work your team agrees to do.

Google Calendar

Check selected calendars for busy periods before offering supported widget or phone bookings.

Microsoft 365 Calendar

Plan a Microsoft 365 Calendar connector for selected calendar availability, with private event details kept out of customer conversations.

Calendly

Plan your Calendly integration with Message. Share a Calendly scheduling link during support, or build a custom workflow around booking events when your team needs more context.

Zoom

Plan your Zoom integration with Message. Share a Zoom meeting link when a support issue needs a walkthrough. Keep the support request and follow-up in Message.

Google Meet

Plan your Google Meet integration with Message. Share a Google Meet meeting link when a support issue needs a walkthrough. Keep the support request and follow-up in Message.

Google Analytics 4

Send supported widget events to GA4 after analytics consent, without putting transcripts or contact details into analytics.

Mixpanel

Plan your Mixpanel integration with Message. Build a controlled event pipeline from Message to Mixpanel. Measure support activity alongside your own product events without exporting whole conversations.

Plan your Segment integration with Message. Build a controlled event pipeline from Message to Segment. Measure support activity alongside your own product events without exporting whole conversations.

Plan your Amplitude integration with Message. Build a controlled event pipeline from Message to Amplitude. Measure support activity alongside your own product events without exporting whole conversations.

Plan your Fullstory integration with Message. Use a permitted Fullstory session link to help your team investigate a customer-reported issue. A custom implementation can associate that link with the right support request.

PostHog

Plan a PostHog connection for consent-aware support events and selected troubleshooting context, with customer data minimized.

Hotjar

Plan a Hotjar connection focused on permitted troubleshooting references, so support can investigate friction without copying recordings.

Matomo

Plan a Matomo integration with a small, consent-aware support event schema and a clearly chosen analytics destination.

Zapier

Use the supported Message triggers and actions to route operational work into the tools your team already uses.

n8n

Install the Message node on self-hosted n8n to run task agents, retrieve results and read recent conversation activity with scoped credentials.

Make

Use Make HTTP tools with Message automation endpoints. Choose a supported event, map the fields and keep control of every action.