Connect an Agent to Discord

1. Open the Discord Developer Portal.
2. Create a new application, or open an existing application.
3. Open the application's Bot page.
4. Create the bot if one does not already exist.
5. Reset or copy the bot token.
6. Store the token securely for entry into the Communication Connection.

Application name: Agent Barn Support
Application ID:   123456789012345678

Resetting the token invalidates the previous value immediately. If a Connection already uses the old token, update it before or right after the reset.

Open Bot → Privileged Gateway Intents and enable:

• Message Content Intent

Message Content Intent is required for Agent Barn to receive the content of Discord messages. Without it, messages arrive without readable text and the Agent cannot act on them.

Also consider Server Members Intent:

• Enable it when the Connection editor must suggest server members.
• It is relevant to member discovery and user-based access configuration.
• It is not required when you are not using member discovery.

Reconnect the bot after changing its enabled intents so Discord applies the new configuration.

1. Open OAuth2 → URL Generator.
2. Select the bot scope.
3. Generate an installation URL.
4. Open the URL and choose the intended Discord server.
5. Grant the bot the required permissions.
6. Repeat the installation for every server the Connection should use.

Installing the bot requires Discord authority in that server. If you cannot complete the install, ask a server administrator to open the generated URL.

With the token in hand, create the Connection on the Agent.

1. Open the existing Agent.
2. Open its Communication Connections section.
3. Choose Discord.
4. Enter a Connection display name.
5. Paste the Discord bot token into Bot token.
6. Configure the server, channel, user, role, direct-message, and mention policies.
7. Create and enable the Connection.

Use a display name that identifies the server or purpose, such as Discord: Community server.

The token must not be reused by another active Discord Communication Connection. The Communications Gateway validates the token and owns the Discord Gateway lifecycle for this Connection.

A saved Discord Connection can browse provider-backed directory data using its stored credential, so you can pick servers, channels, members, and roles instead of collecting IDs by hand.

1. Save the Discord Connection.
2. Open the Connection for editing.
3. Use Browse for Allowed servers.
4. Select a server before browsing its channels, users, or roles.
5. Use the resulting searchable pickers to populate the policy fields.

Directory discovery can return:

• Servers where the bot is installed
• Message-capable channels in the selected server
• Human server members
• Non-default roles

How it behaves:

• Bot accounts are excluded from member suggestions.
• Non-message channels are excluded from channel choices.
• Only Discord provider IDs are persisted.
• Manual ID entry remains available.
• Raw IDs may still be used for multi-server allowlists.
• Provider directory results are credential-scoped and cached briefly.

A directory failure does not expose the bot token or raw provider error text, and it does not stop you from configuring policies manually.

Browsing is server-first: select the server before its channels, members, and roles can be listed.

Manual entry remains a supported alternative to browsing.

1. Open Discord user settings.
2. Open Advanced.
3. Enable Developer Mode.
4. Use Discord's context menus to copy server, channel, user, and role IDs.

Server ID:  234567890123456789
Channel ID: 345678901234567890
User ID:    456789012345678901
Role ID:    567890123456789012

Policy fields require Discord IDs rather than display names. A server, channel, user, or role name cannot be used as an access identifier.

The Discord Platform Plugin supplies these settings on the Connection form.

Users and roles

For server messages, when Allowed users or Allowed roles are configured, a sender is admitted if either condition holds:

• Their user ID is allowed, or
• They hold at least one allowed role.

Both conditions are not required. A role ID is used purely as an interaction boundary, and role names cannot replace the numeric ID.

allowed_user_ids:
456789012345678901

allowed_role_ids:
567890123456789012, 890123456789012345

Direct messages

Direct messages default to off, but they are configurable and not permanently disabled. Set open to accept messages from any Discord user, or allowlist to accept them only from Allowed users.

Alert channel and scheduled messages

The connection form includes an optional Alert channel field. The built-in runtime adapter does not use this setting to route independently scheduled output to Discord.

The adapter sends replies through the connection and destination of an existing incoming delivery. Setting Alert channel therefore does not enable scheduled notifications through this adapter. A separate integration needs its own documented delivery setup.

Configuring the field does not grant the bot Discord permission to access that channel; the bot must already be able to see and post there.

Recommended production configuration

group_policy:         allowlist
guild_ids:            One or more approved server IDs
allowed_channel_ids:  Explicitly configured
allowed_user_ids:     Explicitly configured, or empty
allowed_role_ids:     Explicitly configured, or empty
require_mention:      Enabled
dm_policy:            off
home_channel_id:      Optional approved channel

Start narrow, then widen after the first successful exchange. See Configure channel access for policy guidance.

Confirm the Connection is enabled and its Gateway session is healthy, then test from a controlled channel.

Then confirm the exchange in Agent Barn:

1. Open the Agent.
2. Open Conversations.
3. Select this Discord Connection.
4. Confirm the inbound message and outbound response appear under it.

See Verify your Agent for the full layered verification.