Connect Discord
Get your operators replying on Discord. DMs and @mentions in your server route to your guild.
This tutorial walks you through installing Guilde's Discord bot to your server and validating the round-trip.
Prerequisites
- A Guilde guild (create one)
- A Discord server you own (or can install bots to)
- Admin role in your Guilde guild
Step 1 — Open the Channels page
Inside your guild, sidebar → Channels (or visit /g/<your-slug>/channels
directly). You'll see the available platforms.
Step 2 — Click Add to Discord
Discord's authorize page opens. Pick the server where you want the bot. Authorize.
Behind the scenes:
- Discord redirects back to Guilde with the server ID and an OAuth code.
- Guilde records the connection: this Discord server now routes to this Guilde guild.
- The bot joins your server and is immediately reachable.
You land back on the Channels page with a banner: "Connected discord successfully." The connection appears in the Connected section with the server's name and icon.
Step 3 — Test the routing
Two paths to test:
DM the bot — open Discord, find the bot in the Members list, send it a direct message. ⚠️ Direct messages aren't currently routed (this is intentional — DMs without a server context can't resolve to a guild). The bot will reply that you should @-mention it in a channel instead.
@-mention in a channel — open any channel where the bot has access,
type @<botname> hi. The mention should:
- Trigger Guilde's webhook
- Stream a reply from your guild's operator
- Post the reply back in the same Discord thread
If the operator replies, the integration is working end-to-end. ✅
Troubleshooting
The bot replies but says "this server isn't linked" — the connection
didn't save correctly. Disconnect on the Channels page, re-do the OAuth
install. If it persists, check the API logs for an error during the
callback (/api/channels/discord/callback).
The bot doesn't reply at all — check the Discord Developer Portal for your bot:
- Bot tab → Privileged Gateway Intents → Message Content Intent must be ON. Without this, the bot literally can't read your message.
- The bot must have permission to read the channel you're testing in.
The bot responds but the answer is generic — your guild might not have a default operator wired up to receive Discord traffic. Check that at least one operator exists in the guild (Operators page).
Disconnecting
Channels page → click the connection row → Disconnect. Routing stops immediately. The bot stays in your Discord server — Guilde can't kick it on your behalf. To fully remove, kick the bot from Discord's Members list.