# Integrations URL: /integrations Type: concept Description: Connect your tools so Stylo can pull customer data and take actions across your stack. Keywords: integrations, zendesk, shopify, stripe, slack, connect Integrations let Stylo access data from your existing tools — order details from Shopify, subscription info from Stripe, customer records from HubSpot — and use it when generating responses. They also enable workflows to take actions in external systems, like creating a Jira ticket or sending a Slack notification. Available integrations [#available-integrations] E-commerce [#e-commerce] | Integration | What it provides | | --------------- | ----------------------------------------------------------------- | | **Shopify** | Order details, customer history, fulfillment status, product info | | **WooCommerce** | Orders, customers, store data | | **Stripe** | Payment history, subscription status, invoices, refund info | CRM & Support [#crm--support] | Integration | What it provides | | -------------- | --------------------------------------------------------------------------------------- | | **Zendesk** | Ticket management, user lookup, search — connected automatically when you install Stylo | | **HubSpot** | Contacts, deals, tickets, company data | | **Intercom** | Conversations, customer data | | **ServiceNow** | Incidents, requests, service catalog items | Project Management [#project-management] | Integration | What it provides | | -------------- | ------------------------------------------------- | | **Jira** | Create and track issues from support interactions | | **Linear** | Create and sync issues with engineering teams | | **Monday.com** | Manage boards and items from workflows | Communication [#communication] | Integration | What it provides | | --------------------- | ---------------------------------------------------- | | **Slack** | Send messages and notifications to channels or users | | **Gmail** | Send and receive emails from workflows | | **Microsoft Outlook** | Connect email and calendar via Microsoft 365 | | **Resend** | Send transactional emails from workflows | Content & Knowledge [#content--knowledge] | Integration | What it provides | | ------------ | --------------------------------------------------- | | **Notion** | Sync pages and databases for knowledge context | | **Google** | Access Sheets, Docs, and Drive for data and content | | **Webflow** | CMS content and form submissions | | **Typeform** | Form responses and survey data | Developer [#developer] | Integration | What it provides | | ------------- | -------------------------------------------------- | | **GitHub** | Pull context from repos, issues, and pull requests | | **Firecrawl** | Web scraping and crawling for knowledge ingestion | Connecting an integration [#connecting-an-integration] 1. Go to **Integrations** in the Stylo sidebar navigation 2. Find the integration you want to connect 3. Click **Connect** 4. Follow the authentication flow: * **OAuth integrations** (most integrations) — A popup opens where you sign in and grant Stylo access. Tokens are managed automatically, including refreshes. * **API key integrations** (Stripe, Linear, WooCommerce, Firecrawl, Resend) — Paste your API key or secret in the dialog. Keys are stored encrypted. Once connected, the integration is available to all Response Workflows and general Workflows in your organization. Using integrations in Response Workflows [#using-integrations-in-response-workflows] Response Workflows use integrations through **tools**. When creating or editing a workflow, you select which tools to enable. For example, enabling the Shopify tool lets the workflow look up order details when generating a response. The AI uses tool data in two ways: * **Template placeholders** — In template mode, tool data fills specific placeholders in your response template * **AI context** — In guided mode, tool data is provided as context so the AI can reference it naturally in the response See [Creating a Workflow](/response-workflows/creating-a-workflow) for setup details. Using integrations in Workflows [#using-integrations-in-workflows] General Workflows have dedicated blocks for each integration. For example: * A **Zendesk / Get Ticket** block fetches ticket details * A **Shopify / Get Order** block retrieves order data * A **Slack / Send Message** block posts a notification * A **Linear / Create Issue** block creates a bug report These blocks can be chained together to build multi-step automations. The output of one block flows into the next as input. Integration status [#integration-status] Each connected integration shows its current status: | Status | Meaning | | ---------------- | ------------------------------------------------------------- | | **Connected** | Working normally | | **Auth expired** | OAuth token needs to be refreshed — click to re-authenticate | | **Error** | Connection failed — check credentials or integration settings | | **Disconnected** | Not yet connected | Managing integrations [#managing-integrations] From the integration detail page, you can: * **Re-authenticate** — Refresh expired OAuth tokens or update API keys * **Disconnect** — Remove the integration entirely. This does not delete data already used in responses, but workflows that depend on this integration will no longer be able to fetch data from it. Tips [#tips] * **Connect e-commerce integrations first.** Shopify, Stripe, and WooCommerce provide the richest data for support responses — order status, shipping info, payment details. * **Start with what your agents look up manually.** If agents regularly switch to another tool to find information, that's an integration worth connecting. * **Use Slack for visibility.** Connect Slack to get notifications when workflows execute, when drafts are waiting for review, or when escalations happen. Related [#related] * [Managed APIs](/managed-apis) * [MCP Servers](/mcp-servers) * [Security and Data Handling](/security-and-data-handling) * [Getting Started](/getting-started)