> ## 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

> Choose the right Woes integrations for support channels, context, workflow handoff, and operator tooling.

# Integrations

Woes integrations connect the tools your team already uses to the support
workspace. Use them to bring messages into the inbox, add grounded context,
or hand work to engineering.

This page is organized by the job each integration helps you do.

## Pick By Workflow

| Workflow            | Integrations                                                       | Use them for                                                                              |
| ------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- |
| Support channels    | [Discord](./discord), [Slack](./slack)                             | Bring community, customer-channel, and direct-message support into the shared inbox.      |
| Context sources     | [GitHub](./github), [Confluence](./confluence), [Notion](./notion) | Import docs, runbooks, examples, and internal support knowledge into the Context Library. |
| CRM context         | [HubSpot](./hubspot)                                               | Give operators account, contact, deal, owner, and lifecycle context during support.       |
| Product handoff     | [Jira](./jira), [Linear](./linear)                                 | Create linked engineering issues from support work and keep lifecycle status visible.     |
| Workflow automation | [Zapier](./zapier), [Webhooks](./webhooks)                         | Connect no-code workflows or send signed support events to your own systems.              |
| Error context       | [Sentry](./sentry)                                                 | Let operators confirm the connected Sentry organization and available projects.           |

<Tip>
  Start with the channels where customers already ask for help, then add the
  context sources operators need to answer those questions accurately.
</Tip>

## Connectors

| Connector                  | Best for                                                              | Main setup surface        |
| -------------------------- | --------------------------------------------------------------------- | ------------------------- |
| [GitHub](./github)         | Repository examples, SDK docs, changelogs, and implementation notes.  | Context Library           |
| [Discord](./discord)       | Developer community support and selected server channels.             | Channels > Discord        |
| [Slack](./slack)           | Shared-channel support, DMs, app mentions, and emoji-created tickets. | Channels > Slack          |
| [Jira](./jira)             | Atlassian engineering handoff from Woes issues.                       | Integrations > Jira       |
| [Linear](./linear)         | Product and engineering handoff with linked Linear issues.            | Integrations > Linear     |
| [Confluence](./confluence) | Spaces, runbooks, and support knowledge stored in Atlassian.          | Integrations > Confluence |
| [HubSpot](./hubspot)       | Operator-only CRM account and contact context.                        | Integrations > HubSpot    |
| [Notion](./notion)         | Product notes, FAQs, playbooks, and launch guidance.                  | Integrations > Notion     |
| [Zapier](./zapier)         | No-code triggers, searches, and actions over Woes records.            | Integrations > Zapier     |
| [Webhooks](./webhooks)     | Signed outbound support events with retries and delivery history.     | Integrations > Webhooks   |
| [Sentry](./sentry)         | Operator visibility into connected Sentry organization and projects.  | Integrations > Sentry     |

## How Setup Usually Works

<Steps>
  <Step title="Connect the integration">
    Open **Workspace Settings -> Integrations**, choose the connector, and
    approve access in the external tool.
  </Step>

  <Step title="Choose what Woes can use">
    Select channels, repositories, pages, spaces, teams, projects, or records
    depending on the integration.
  </Step>

  <Step title="Attach it to the right workflow">
    Channel integrations route into Inbox. Context integrations appear in
    Context Library. Workflow integrations appear on Issues and Automations.
  </Step>

  <Step title="Test with a real workflow">
    Send a message, import a source, create a linked issue, or run a Zap before
    relying on the integration in production.
  </Step>
</Steps>

## Connector principles

* Customer connectors should be workspace-scoped and safe to install, disconnect, audit, and troubleshoot from Woes.
* Context connectors should add evidence for operators and agents without exposing credentials or private data to customers.
* Workflow connectors should make ownership clear and avoid duplicate linked work.
* Channel connectors should use the same inbox, routing, SLA, assignment, and analytics model as live chat and email.
* Customer-facing docs should explain what a workspace admin can configure and what operators can use after setup.

## What belongs elsewhere

| Surface                                                                        | Where it belongs                                |
| ------------------------------------------------------------------------------ | ----------------------------------------------- |
| Woes subscription billing, invoices, and subscription management               | [Billing](/settings/billing)                    |
| Email domain setup, provider delivery, inbound receiving, and channel behavior | [Email channel](/channels/email)                |
| Live chat widget installation, launch behavior, identity, and visual setup     | [Chat Widget](/chat-widget/overview)            |
| Public REST API and remote MCP usage from customer backends                    | [API Reference](/api-reference/overview)        |
| Technical route-family boundaries                                              | [Route boundaries](/developer/route-boundaries) |

## Where to manage connectors

Use **Workspace Settings -> Integrations** for connection state and
connector-level actions. Use **Context Library** for GitHub, Notion,
Confluence, and synced HubSpot source management. Use channel settings pages for
live chat, email, Discord, and Slack behavior after a connector is installed.