Discord
1. Prerequisites
- A Discord account with permission to create applications
- Admin permissions on the Agentic Engine platform
- An existing Discord server to add the Bot to
2. Create a Discord Bot and get credentials
Go to Discord Developer Portal and follow these steps:
- Click New Application, enter an application name, and create it.
- Open the application details and switch to the Bot tab in the left navigation.
- On the Bot page, click Reset Token to generate a Bot Token, and then copy and save it (The token is shown only once. Save it right away.).
- On the Bot page, turn on the following Privileged Gateway Intents switches:
| Permission name | Required | Description |
|---|---|---|
| Message Content Intent | Required | Allows the Bot to read message content |
| Server Members Intent | As needed | Gets server member information |
| Presence Intent | As needed | Gets user online status |
You must turn on Message Content Intent. Otherwise, the Bot can't read the content of user messages and won't work properly.
- To support user OAuth binding, go to OAuth2 > General in the left navigation, note down the Client ID and Client Secret, and add the callback URL to Redirects:
https://<your-domain>/api/discord-oauth/callback
The Bot Token has full Bot operation permissions. Don't commit it to a code repository or share it with others. If the token is leaked by accident, reset it in Discord Developer Portal right away and update the platform configuration.
3. Add a Discord channel in the platform
As an admin, log in to Agentic Engine and go to System Admin > Channels:
- Click New Channel and select Discord as the channel type.
- Fill in the following configuration items:
| Config items | Required | Description |
|---|---|---|
| Channel Name | Required | Display name, such as "Discord Server" |
| Bot Token | Required | Access token of the Discord Bot, used to connect to the WebSocket Gateway and send messages |
| Client ID | Optional | Client ID of the Discord application, used only for the OAuth user binding flow |
| Client Secret | Optional | Client Secret of the Discord application, used only for the OAuth user binding flow |
| Default Model | Optional | If left empty, the system default model is used |
| Channel Input Suffix | Optional | Appended to each round of channel input as additional instructions. It doesn't replace the Agent's own system prompt. |
Note: One company can configure multiple Discord channel instances, but the same Bot identity can't be configured more than once in the same runtime environment.
4. Bind a Discord account
If the admin has filled in the Client ID and Client Secret in the channel configuration, regular users can bind their own Discord accounts in Channel Accounts:
- Open the user menu, go to Channel Accounts, find the corresponding Discord channel instance, and click Bind.
- The system redirects you to the Discord OAuth authorization page. Log in to your Discord account and click Authorize.
- After authorization succeeds, you're automatically redirected back to the platform, and the binding status changes to Bound.
After binding, messages that you send to the Bot in Discord are linked to your platform account. To unbind, find the instance in Channel Accounts and unbind it.
5. FAQ
Abnormal channel status / Bot can't connect
- Check that the Bot Token is valid (hasn't been reset).
- Make sure that the Bot has been invited to the target Discord server.
- Make sure that Message Content Intent is turned on in Developer Portal.
OAuth callback failure
- Make sure that the callback URL has been added to the OAuth2 > Redirects whitelist of the Discord application.
- The callback URL must exactly match the platform's actual deployment domain, including the protocol (https) and path.
Users can't bind Discord accounts
- Make sure that the Client ID and Client Secret are filled in in the channel configuration (OAuth binding is unavailable if either is missing).
- Make sure that the OAuth callback URL is configured correctly.
Bot doesn't receive messages
- Make sure that Message Content Intent is turned on. Otherwise, the Bot can't get message content.
- Make sure that the Bot has the Read Messages and Send Messages permissions in the target channel.
Related pages and next steps
- See the setup instructions for other platforms: Channel management.
- Learn about the overall flow of channel connection and binding: Channel overview and binding.
- Configure the Agent to use: Agent.
- See how to use conversations in the platform: Conversations.