Discord Channel Setup

Use Discord when your team works in servers and threads. A workspace owner connects Discord once, then the workspace binds the channels that should route to specific agents.

Before you start

• A Dawn workspace and at least one agent profile.
• A workspace owner who can configure Discord once for the workspace.
• If you use a custom app, a Discord application with a bot user, its application ID, and a valid bot token.
• A Discord server where the bot is installed and can see the target channel.

1) Choose the workspace Discord app

Discord is configured once per Dawn workspace. After that, the workspace can add one or more Discord channel bindings.

1. Open Channels → Add channel → Discord.

2. If no Discord app is configured yet, Dawn shows:

   • Standard Dawn App when your deployment exposes the official app.
   • Custom app when you want a dedicated Discord bot for this workspace.

3. Only workspace owners can set up or change the workspace Discord app.

4. After Discord is configured, other workspace members can add Discord bindings.

2) Standard Dawn App

1. Select Standard Dawn App in Dawn.
2. Continue the setup flow and authorize the official app into the target server.
3. If the wizard says the official app is unavailable for your deployment, switch to the custom app flow.
4. After the app is configured, continue to add channel bindings.

3) Custom Discord app

1. Create a Discord application and bot.
2. Enable Message Content Intent.
3. In Dawn, select Custom app.
4. Enter the Application ID and Bot token.
5. Save the app configuration in Dawn.
6. Use the Invite URL Dawn shows to install the bot into the target server.
7. Make sure the bot can view channels, read message history, send messages, and send messages in threads if you use threads.

4) Get the Guild ID and Channel ID

Dawn currently requires raw Discord IDs. It does not yet provide a Discord channel picker in the UI.

1. Enable Discord Developer Mode.
2. Right-click the target server and copy the Server ID. Use that as the Dawn Guild ID.
3. Right-click the target channel and copy the Channel ID.
4. Paste both values into Dawn.

5) Create the Discord binding

1. Open Channels → Add channel → Discord again.
2. Enter the Guild ID and Channel ID.
3. Choose a trigger mode. Mention only or Mention or DM are the safest defaults for shared servers.
4. Set context mode according to whether Dawn should use recent discussion from that same channel or thread.
5. Create the binding and assign it to the right agent.
6. Test by mentioning the bot in the bound channel and confirm the reply appears in that same channel or thread.

How context works in Discord

• Dawn can use recent discussion it receives in the same channel or thread as later context.
• This depends on the bot being able to read the channel and receive message content.
• Dawn does not currently backfill older Discord history it never saw before the trigger.

Direct messages and linking

• Discord DMs with Dawn are private conversations, separate from shared server channel bindings.
• If you want Dawn to recognize the same person in Discord and Dawn Web, start the link flow in the DM with /link [email protected].
• Use shared server bindings when the conversation should stay visible to the team.

Validation checklist

• A mention in the bound Discord channel produces one reply there and one matching conversation in Dawn.
• The saved Guild ID and Channel ID still match the intended location after refresh.
• A follow-up message in the same thread or channel confirms the selected context behavior.
• If you use Discord threads, one thread-specific test confirms the bot has the required thread permissions.

Troubleshooting

• No reply on mention: check the bot token, bot installation, channel permissions, and whether Message Content Intent is enabled.
• Binding exists but nothing routes: the Guild ID or Channel ID is wrong, or the binding is not assigned to an enabled agent.
• Context is thinner than expected: verify the bot can read message history and the binding context mode is set as intended.
• Threads do not behave as expected: confirm the bot has thread permissions and the parent channel is the one you intended to bind.
• Managers cannot configure Discord: this is expected. Only workspace owners can set up or change the workspace Discord app.

Audit Discord binding health and mention any missing intents/permissions.

Show recent Discord inbound events and processing outcomes.