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

# Discord Connector

> Connect selected Discord developer support activity to the Woes inbox.

# Discord Connector

<img src="https://mintcdn.com/woes/SjmqB9Aiw359c6aC/images/integrations/discord-logo.svg?fit=max&auto=format&n=SjmqB9Aiw359c6aC&q=85&s=0be78712b93461543f25c1c13acc8859" alt="Discord logo" width="56" height="56" data-path="images/integrations/discord-logo.svg" />

Discord brings selected developer-community conversations into Woes so support
questions do not stay trapped in a server.

## At A Glance

| Use Discord for                                                                                       | Where it appears                                   |
| ----------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Community support channels, forum threads, and server messages that should become Woes conversations. | Channels > Discord, Inbox, Automations, Analytics. |

## What it does

Discord helps teams:

* Install the Woes-owned Discord app into a server.
* Select which channels Woes should listen to.
* Create or continue Woes conversations from configured Discord activity.
* Route Discord support through the same inbox, assignment, SLA, automation, and analytics model as live chat and email.

## Where it appears in Woes

* **Workspace Settings -> Integrations** can show Discord as a customer connector.
* **Workspace Settings -> Channels -> Discord** manages install health, channel discovery, intake surfaces, and channel rules.
* **Inbox** shows Discord-origin conversations with channel context.
* **Automations** can branch on Discord events and issue fields.
* **Analytics** can compare Discord volume and outcomes with other channels.

## Recommended setup

* Keep only support-relevant channels enabled.
* Use app mentions or explicit support channels first before expanding to broader intake.
* Choose the agent context that should answer Discord support threads.
* Confirm channel rules after reinstalling or re-inviting the bot.

<Tip>
  Start with mention mode or a dedicated support channel. Expand to broader
  channel intake only after operators are comfortable with the volume.
</Tip>

## Operating Notes

Discord should feed the shared support model. It should not create a separate Discord-only queue or separate AI behavior tree.

## Related docs

* [Discord channel](/channels/discord)
* [Omnichannel Support](/support-workflows/omnichannel-support)
* [When triggers](/platform/automations/nodes/when-triggers)