Discord
Sign-in, the announcement bot, quests that read your server, and roles handed out as rewards.
Five separate features share the name Discord, and turning one on does not turn on the others.
| What you want | What it actually is | Where it is set up |
|---|---|---|
| Fans sign in with their Discord account | A sign-in provider | Per community, by us |
| Fans attach Discord to an account they already have | Account linking | Per community, by us |
| Your server gets a post when you publish something | The FanBase bot | Settings, then Automation |
| A quest that checks a fan joined the server or holds a role | Two quest templates | Discord quests |
| A Discord role given for completing something | A reward type | Rewards |
Sign-in and account linking
These are two different things and they are configured independently.
Sign-in is Discord as a way into your app. A fan taps Continue with Discord and they are in, with no separate password. It sits alongside Google, X, Twitch and Shopify, and you choose which of those appear.
Account linking is a fan who is already signed in attaching their Discord account afterwards, from their profile. It is on by default, because a fan who signed in with Google still needs a linked Discord account before any Discord quest can be checked.
Linking is the one that matters for quests. A fan who signed in with Discord is linked automatically, but a fan who signed in another way is not, and their Discord quests stay blocked until they link. The card handles that itself. See Templates that need a linked account.
Tell your FanBase contact which sign-in methods you want and whether Discord linking should be available, and it is a config change rather than a build. Sign-in methods has the full list.
In-app usernames look like name#1234. That is a FanBase handle in a Discord-like shape, and it is unrelated to the fan's Discord account.
Announcements in your server
The bot posts to one channel in your server when something happens in the app. The announcement goes out whether or not anyone on your team remembers to write one.
| Trigger | What the server sees |
|---|---|
| A quest is published | A post with the quest and a way through to it |
| An event starts | A post when the event opens |
| An event ends | A post when it closes |
Each notification type has its own toggle, so you can announce quests and stay quiet about everything else. More types are being added: newsfeed posts, store changes and event winners are the ones being worked on. In build
Setting it up
Get the bot into your server
Go to Settings, then Automation. Press Connect on the Discord card. Discord asks you to pick the server and approve the bot, then returns you to the admin panel.
Whoever clicks it needs Manage Server on that Discord server, so get that person in the room before you start. If the card already offers Disconnect, the bot is in and you can skip this step.
Choose the channel
Give the channel ID of the channel you want the posts in. A dedicated channel is worth making: announcements in a busy general chat scroll away in minutes.
Choose a role to mention, or none
Optional. Pick a role and every post pings it. Leave it empty and the post is quiet.
Pinging everyone on every quest is how a server learns to mute your announcement channel. If you want a mention, make an opt-in role for fans who asked for it.
Turn on the notifications you want
Toggle them one at a time and leave the rest off. You can come back and add more once you know what the volume looks like.
Publish something and watch the channel
The only real test.
Getting the IDs
Both IDs sit behind Discord's Developer Mode, which Finding the IDs turns on.
| ID you need | How to get it |
|---|---|
| Channel ID | Right-click the channel in the channel list, then Copy Channel ID |
| Role ID | Right-click the role in Server Settings, then Roles, and Copy Role ID |
Check the bot's role can view the channel and send messages in it. A channel the bot cannot post in looks exactly the same as a bot that is not working, and it is the first thing to rule out.
Discord as a source of quests
Two templates read your server rather than write to it.
Join the server asks a fan to be a member of a server you name, and checks it. Hold a role asks for a specific role and checks that too, which is how you reward the people who already earned something in Discord.
Both need the fan's Discord account linked, and both need the server ID. Every field is in Discord quests.
A Discord role is also a gate rather than a quest: you can hide a quest, or block it, until a fan holds a role. That is in Hidden quests and gating.
A Discord role as a reward
The other direction. A fan completes a quest and the bot puts a role on them in your server, with nobody in the loop.
This is what backs the pattern most partners want: level ten in the app buys you a colour in Discord. It needs the bot connected, and the bot's own role has to sit above the role it is assigning in your server's role list. Discord will not let a bot grant a role ranked higher than its own. Check that ordering first if a role is not being assigned.
The reward types you can attach to a quest are in Rewards.