> ## Documentation Index
> Fetch the complete documentation index at: https://docs.woes.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect Woes to the channels, context sources, workflow tools, and APIs your support team already uses.

# Integrations

Integrations bring customer conversations, API context, and support signals into
Woes. Start with the surfaces where your customers already ask questions and
where your API truth already lives.

<Tip>
  For the full connector catalog, use the [Integrations catalog](/integrations-catalog/overview).
</Tip>

## Integration Categories

| Category                          | Woes surface                                                                                                                                                         |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Chat                              | [Live Chat](/channels/live-chat) and [Mintlify widget install](/quickstart/install-widget-mintlify).                                                                 |
| Email                             | [Email](/channels/email) support and survey delivery.                                                                                                                |
| Community                         | [Discord](/channels/discord) and [Slack](/channels/slack) conversations in the Woes inbox.                                                                           |
| Codebase                          | [GitHub Context](/context/github) for docs and SDK examples.                                                                                                         |
| Workspace docs                    | [Notion](/integrations-catalog/notion) pages and [Confluence](/integrations-catalog/confluence) spaces for product notes, FAQs, setup guides, and support playbooks. |
| CRM context                       | [HubSpot](/integrations-catalog/hubspot) records for operator-only account and contact context.                                                                      |
| Product and engineering workflows | [Linear](/integrations-catalog/linear), [Jira](/integrations-catalog/jira), and [Zapier](/integrations-catalog/zapier).                                              |
| Custom event delivery             | [Webhooks](/integrations-catalog/webhooks) for signed support events delivered to your backend.                                                                      |
| Error context                     | [Sentry](/integrations-catalog/sentry) project visibility for operators.                                                                                             |
| Public API                        | [API Reference](/api-reference/overview) for server-side integrations.                                                                                               |

## Setup Order

<Steps>
  <Step title="Connect customer channels">
    Install live chat first, then add email, Discord, or Slack based on where
    customers already contact support.
  </Step>

  <Step title="Connect source context">
    Add docs, specs, repositories, Notion pages, Confluence spaces, and examples
    so agents can answer from real context.
  </Step>

  <Step title="Connect workflow tools">
    Add Linear, Jira, Zapier, Webhooks, Sentry, or HubSpot when operators need
    external product, engineering, automation, event delivery, error, or CRM
    context.
  </Step>

  <Step title="Create keys carefully">
    Use widget public keys in browsers and private REST API keys only from server-side systems.
  </Step>

  <Step title="Test the whole loop">
    Send a customer message, verify it reaches Inbox, check the agent evidence, and confirm analytics update.
  </Step>
</Steps>

## Security Rules

* Keep REST API keys out of client-side apps.
* Keep source auth credentials separate from source content.
* Use verified widget identity for account-specific history.
* Review tenant boundaries before connecting customer data.