← Back to Channels and integrationsOpenClaw channels
Discord setup step by step
Discord setup should be tested in layers: token/runtime health, DM pairing, shared-space visibility, and mention behavior.
Discord ruleDo not confuse “bot is connected” with “bot can reply in the place and way you expect.”
Setup ladder
The order that keeps Discord debuggable
- Confirm token/runtime health. The service must actually be reading the token.
- Test DMs. Pairing and approval rules should be proven first.
- Test a guild/channel mention. Shared-space visibility is a separate question.
- Check mention gating. A healthy bot may still be intentionally quiet without mention.
Common blockers
What usually goes wrong first on Discord
Token path problemThe token exists, but the running service cannot actually use it.
Pairing never completedDMs fail because the sender was never approved or the path was blocked.
Mention gating confusionThe bot is healthy, but shared spaces still require explicit mention.
Open deeper reference links for this page