Connecting Discord requires a few more steps than Telegram, and the key lies in the Developer Portal’s permission configuration. This article lists all the “most easily missed points” based on the official documentation.
Figure: The header image of the official OpenClaw Discord channel documentation page.
1. Create an App in the Discord Developer Portal
- Click New Application.
- Add a Bot.
- Copy the Bot Token (keep it safe).
2. Enable Necessary Intents
In the Bot settings page, enable:
- Message Content Intent (Required)
- Server Members Intent (Recommended)
- Presence Intent (Optional)
3. Generate Invite Link and Add to Server
In the OAuth2 URL Generator, check at least:
botapplications.commands
Common basic permissions to check:
- View Channels
- Send Messages
- Read Message History
- Embed Links
- Attach Files
Do not grant Administrator directly unless you are absolutely certain of the risks.
4. Obtain IDs (for Configuration and Auditing)
Turn on Developer Mode in the Discord client and copy:
- server ID
- channel ID (Optional)
- user ID
The official recommendation is to prioritize using numeric IDs in the OpenClaw configuration for more stable auditing.
5. Integration on the OpenClaw Side
It is recommended to use onboarding/configure to complete the token and routing configuration:
openclaw onboard# Oropenclaw configureAfter connecting, check the status:
openclaw channels status --probeopenclaw logs --follow6. Common Troubleshooting
- Bot is online but doesn’t reply: Mostly likely missing intents or permissions.
- Commands are visible but execution fails: Usually rejected by OpenClaw’s authorization/allowlist.
- Works in groups but not in DMs: Check “Allow direct messages from server members” and policy configurations.
- Prompt says plugin unavailable: Follow the prompt on the official channel page and run
openclaw channels status --probeto see what exactly is missing.
7. Security and Operation Recommendations
- Store the token in a controlled configuration; do not commit it to the repository.
- Keep command authentication enabled by default.
- Roll out to a single test channel first before expanding to the entire server.
Summary
The core difficulty of Discord integration is not the “number of steps,” but “aligning permissions.” Once you align the intents, scopes, bot permissions, and OpenClaw authorization policies, it will run very stably.
Reference Links
- Discord Channel Docs:
https://docs.openclaw.ai/channels/discord - Slash Commands:
https://docs.openclaw.ai/slash-commands - Channels Overview:
https://docs.openclaw.ai/channels/index
Further Reading
If this article helped you, please share it with others!
Some information may be outdated