How to create your own Discord bot
You create an application in the Discord Developer Portal, copy its token into SCNX and invite the bot to your server. That takes about two minutes at a computer. The steps below name every button you click, the settings you should leave alone and the errors people run into.
Updated 2026. november 18.10 min read
On this page
The short version
- You register the bot with Discord yourself, so it is your application with your name and avatar.
- You paste its token into SCNX once. SCNX switches on the intents the bot needs and hosts it from then on.
- The bot, its modules and the hosting are free on our Starter plan.
What you need
- A Discord account
- A server you own. Adding a server also works with the Administrator permission, but only the owner or a co-owner can create its bot
- About two minutes at a computer. It works on a phone, it just takes longer
What you are creating
A Discord bot is a program that logs in to Discord under its own account, the one with the APP tag next to its name. Someone has to write that program and someone has to keep it running.
On SCNX the program already exists and we run it. The bot is still registered to your Discord account and carries your name, but welcome messages, levels, tickets or moderation are modules you switch on in a dashboard. If you would rather write the program yourself, the last section is for you.
Step 1: Add your server to SCNX
Log in with Discord
Open the SCNX dashboard and choose Login with Discord. Your Discord account is the only account you need.
Pick your server
You see the servers you can manage. Select the one the bot is for. You can add it if you own it or have the Administrator permission there. A server you created a minute ago shows up after Refresh data at the bottom of the page.
Accept the two documents
You confirm our Terms of Service and the Data Processing Agreement, once per server. Tick both boxes and the button below them unlocks.
The server now has its own dashboard. From here on you need to be the server owner, or a co-owner the owner has named under trusted admins. Everyone else sees a note that only the owner can enable the bot.
Step 2: Create the application in the Developer Portal
Every bot on Discord belongs to an application that someone registered. Registering it yourself is what makes the bot yours: it has its own name and avatar and shares them with nobody.
Create a new application
Open the Discord Developer Portal and click New Application in the upper right. Type a name, accept Discord's developer terms and confirm with Create. The name can be changed later.
Open the Bot page
Click Bot in the menu on the left. You could set a name and avatar here, but you don't have to. SCNX has a profile editor for that.
Reset the token and copy it
Still on the Bot page, click Reset Token and confirm. Discord may ask for your 2FA code. Copy the token right away. Discord shows it once, and if you lose it you reset it again.
- Use a fresh application
- An application that already runs another bot will not work, and neither will the one your Support Bot uses. Each bot needs its own.
- Leave Requires OAuth2 Code Grant off
- With that switch on, Discord refuses the invite later. If it is on, the dashboard warns you as soon as the bot is created.
- Leave the Interactions Endpoint URL empty
- That field on the General Information page is for bots that receive commands over a web address. With a value in it, your bot can't answer slash commands or buttons.
The token is your bot's password. Paste it into the SCNX dashboard and nowhere else. Don't send it to other admins, and our staff will never ask for it.
Step 3: Paste the token into SCNX
Open Discord-Bot
In your server's dashboard, click Discord-Bot in the sidebar. The first page repeats the Developer Portal steps with a short video. You have done them, so click I have created a bot.
Enter the token
Paste the token into the field Your Bot-Token and tick the box for the Bot Hosting Service Agreement.
Create the bot
Click Check my token & create bot. SCNX checks the token, configures the bot with Discord and sets up its hosting. You see those three steps tick off, which takes a few seconds.
While it configures the bot, SCNX also switches on the privileged intents for you. You don't have to switch them on in the Developer Portal yourself. More on intents below.
Step 4: Invite the bot to your server
Open the invite
The page now says Your bot is ready! and shows the bot's name. Click Add the bot to your Discord. Discord's authorization screen opens in a new tab with your server already selected.
Authorize it
Click Continue, then Authorize. The invite asks for the Administrator permission. You can untick it, but then every module that needs a permission you left out fails with a Missing Permissions error, so we recommend keeping it.
Go to the dashboard
Back in SCNX the other buttons are now active: Edit Bot Profile, Enable modules and Take me to my dashboard.

Screenshot from our test server. Your dashboard may look different.
The bot now shows as online in your member list. Its status card in the dashboard is where you reload the configuration, restart the bot, stop it or read its logs.
One thing to do in Discord right away: open Server Settings, go to Roles and drag the bot's role above the roles it should hand out or moderate. Discord never lets a bot touch a role that sits above its own, even with Administrator.
Intents, and when you have to touch them
Intents are Discord's switches for what a bot is told about. Three of them are privileged, which means they stay off until someone turns them on: Presence Intent, Server Members Intent and Message Content Intent. Without them a bot is not told when someone joins, can't read messages for levels and auto moderation, and can't see who is online.
SCNX turns all three on when it creates your bot. You find them on the Bot page of your application under Privileged Gateway Intents, and normally you never go there.
If someone switches them off later, your bot can't start. The dashboard then shows Discord refused to start your bot with the fix: open the Bot page, enable the three intents, save, and start the bot again.
Some modules need extra Discord access that can only be added while the bot starts. When you enable one of those, the dashboard says Restart needed to finish enabling and offers to restart. Until then the rest of the bot keeps working.
Set the name and avatar
Click the bot's name on its status card to open the profile editor. You can also reach it through More options, then Edit Bot-Profile. It has the name, the profile picture, the banner and the About me text, with a live preview next to them. Discord can take a few minutes to show the change.
A bot's profile can only be changed every so often, so set the name and the picture in one go. The status line under the bot's name is a separate setting: you find it as Bot-Status in the bot's configuration.
Most servers name the bot after themselves or after a mascot. The bot in the pictures here is called Lantern, after its server, Lantern Lounge.

Screenshot from our test server. Your dashboard may look different.
Switch on your first modules
A new bot does nothing until you tell it to. Open Discord-Bot, then Modules. More than 65 modules come with the bot, each with its own switch and its own settings page. Flip the switches you want and save. Your changes are applied together and the bot reloads once, without going offline.
These four are where most servers start:
| Module | What it does |
|---|---|
| Welcome and Boosts | Greets new members, gives them roles and thanks boosters. Guide |
| Level-System | XP for messages and voice time, role rewards and a leaderboard. Guide |
| Moderation & Security | Warn, mute, kick and ban, plus auto moderation and anti-raid. Guide |
| Ticket-System | Members open a ticket and talk to your team in private. Guide |
Illustration. The real interface may look different.
After you change a module's settings, save and use Reload configuration on the status card. The bot picks up the changes and stays online. Restart bot takes the bot offline for a moment and is only needed for updates or when the dashboard asks for it.
New slash commands don't always appear at once. Discord can take up to an hour to show them, and restarting your Discord app often helps.
If no module covers what you have in mind, there is Custom Commands V3, currently in beta. You describe the feature to your AI assistant or build it in a visual editor, and it runs on the same bot. Our guide on building a bot with AI covers that.
What the free plan includes
Our Starter plan is free and includes the bot with all of its modules, 24/7 hosting, the dashboard, manual server backups, up to 10 custom command triggers and a monthly allowance of AI Coins for the AI modules. It is paid for by ads: every 14 days someone on your team watches a short ad video in the dashboard. Miss it and the bot goes offline until someone watches the video.
Our paid plans drop the ads and the check-in, raise the limits and add a separate Support Bot. The plans page has the details.
When something doesn't work
- "This token seems to be invalid"
- You probably copied the Application ID, the Public Key or the Client Secret. The token only appears on the Bot page after Reset Token. Reset it once more, copy it and paste it again. After a few failed tries SCNX makes you wait before the next one.
- The token is already in use
- Your Support Bot on SCNX runs on that application. Create a second application for this bot and use its token.
- The invite doesn't work
- Turn off Requires OAuth2 Code Grant on the Bot page of the Developer Portal and open the invite again.
- Your server is missing from the list
- Only servers you own or have Administrator on can be added. Use Refresh data if you just created the server or just got the permission.
- The bot is in the server but shows as offline
- Open the status card. If the bot is stopped, click Start bot. If it says Online, wait: Discord can take up to five minutes to update the green dot.
- The bot is online but doesn't answer
- Check that the module is switched on and saved. Then check the channel: the bot needs View Channel, Send Messages and Embed Links there. For roles, its own role has to sit above the role it should assign.
- Slash commands and buttons say the interaction failed
- Clear the Interactions Endpoint URL field in the Developer Portal and restart the bot.
The Error-Log on the status card usually names the module and the missing permission. Our docs have a longer troubleshooting page for everything else.
When writing your own code is better
SCNX bots are made for your own community. A bot you create here only works on the server it was created for, so you can't build a public bot that thousands of other servers invite. If that is the plan, you need your own code.
The same goes if you want to learn programming, or if you need full control over every line. Start with the official guide of discord.js or discord.py and read our guide on keeping a bot online 24/7, because a bot you wrote needs a machine that runs it.
Common questions
- Is it really my own bot?
- Yes. The application is registered to your Discord account, and the name, avatar, banner and About me are yours to set. SCNX runs it for you.
- Do I need to know how to code?
- Not for the bot and its modules. You set those up with switches and forms. Custom Commands V3 has a visual editor for your own logic, and you can leave the building to your AI assistant.
- Do I need to keep my computer on?
- No. The bot runs on our servers in Europe, whether your computer is on or off.
- Do I have to enable intents in the Developer Portal?
- No. SCNX switches on Presence, Server Members and Message Content when it creates the bot. You only go there if someone turned them off and the dashboard tells you the bot can't start.
- What if my bot token leaks?
- Reset it on the Bot page of the Developer Portal, which makes the old token useless. Then open More options on the status card, choose Change Bot-Token and paste the new one. Only the server owner can do that.
- Can I use an application I already have?
- Only if nothing else runs on it. An application that already powers another bot, or your Support Bot on SCNX, can't be shared. Creating a second one takes a minute.
- Can other servers invite my bot?
- No. A bot on SCNX belongs to one community and only works on the server it was created for. For a public bot you need your own code and your own hosting.
- Can I change the bot's name and avatar later?
- Yes, in the profile editor of the dashboard. Discord limits how often a bot's profile can change, so don't rename it five times in an afternoon.
Start with a free bot
Log in with Discord, add your server and create your bot. The dashboard walks you through each step.
Get started for freeFree on our Starter plan. A short ad video every 14 days keeps the bot online.