Discord bot token
Run Flake under your own bot. Paid tier.
A custom Discord bot replaces the shared Flake bot with one that uses your server’s name and avatar. Same features, your own identity. You only need this on the paid tier.
What the token does
The bot token is how Discord identifies a bot application. Flake uses it to read events, post messages, and manage the roles and channels you’ve granted it.
- Secure Authentication
- Your bot token provides secure authentication with Discord's API
- Full API Access
- Token grants access to all Discord features your bot needs
- Easy Integration
- Simply paste your token into Flake to connect your Discord server
- Permission Control
- Configure exactly which permissions your bot requires
- Server Management
- Manage multiple Discord servers with individual bot tokens
- Real-time Updates
- Instant synchronization between Discord and Flake platform
Six steps in the Developer Portal
Six steps from a brand-new Discord application to a token pasted into Flake. Each step matches a screen in the Developer Portal.
- 01
Visit Discord Developer Portal
Navigate to Discord's application management portal
- 01Go to https://discord.com/developers/applications
- 02Log in with your Discord account
- 03This is where you'll create and manage your bot applications
- 02
Create New Application
Set up a new Discord application for your bot
- 01Click the "New Application" button in the top-right corner
- 02Enter a name for your bot (e.g., "My Server Bot")
- 03Click "Create" to proceed to the application dashboard
- 04This name will be visible to users when the bot joins servers
- 03
Configure Bot Settings
Set up your bot's basic information and avatar
- 01Navigate to the "Bot" section in the left sidebar
- 02Click "Add Bot" to convert your application into a bot
- 03Upload an avatar image for your bot (optional)
- 04Set a username for your bot that users will see
- 04
Copy Bot Token
Retrieve your bot's authentication token
- 01In the Bot section, find the "Token" area
- 02Click "Reset Token" if this is a new bot, or "Copy" if the token is already visible
- 03Store this token securely - it's like a password for your bot
- 04Never share this token publicly or commit it to version control
- 05
Enable Gateway Intents
Configure the data your bot can access from Discord
- 01Scroll down to the "Privileged Gateway Intents" section
- 02Enable "Server Members Intent" to access member information
- 03Enable "Message Content Intent" to read message content
- 04These intents are required for most Flake features to work properly
- 06
Add Token to Flake
Connect your Discord bot to the Flake platform
- 01Log into your Flake dashboard at flake.gg
- 02Navigate to "Add Server" or "Discord Integration"
- 03Paste your bot token in the designated field
- 04Flake will automatically invite your bot to your server with the correct permissions
ready to set it up
Open the Flake dashboard and paste the token.
The custom-bot field is under Integrations on your server. Flake will invite the bot with the right scopes the first time you save.
Required and optional permissions
Required permissions are the minimum Flake needs to function. The optional ones add moderation, file attachments, and richer message embeds.
- Send Messagescore
Required for the bot to send messages in channels
required
- Read Message Historycore
Allows the bot to read previous messages for context
required
- Manage Messages
Needed for moderation features like deleting messages
optional
- Embed Linkscore
Allows the bot to send rich embed messages
required
- Attach Files
Required for sending images and file attachments
optional
- Use Slash Commandscore
Enables modern Discord slash commands
required
Token security
Discord tokens grant the bot’s full identity. Treat them the way you’d treat a production database password.
rules
- 01Keep It Secret: Never share your bot token publicly or in screenshots
- 02Regenerate If Compromised: If your token is exposed, immediately reset it in the Developer Portal
- 03Limit Permissions: Only grant the minimum permissions your bot actually needs
Common issues
still stuck
Talk to the people who wrote the code.
Support is run by the same team that ships the product. Both rooms below are watched during working hours, and answers do not go through a tier-one queue.