First Bot Quickstart (Step by Step)

This guide is designed for first-time bot creators. Follow each step in order and you should have a working command in Discord in one short session.

Step 1 - Open the right pages

Open two tabs side by side: Mage.Party Apps page and Discord Developer Portal athttps://discord.com/developers/applications.

In Discord, open your application. In Mage.Party, click Create App to bootstrap from bot token.

Step 2 - Create app with bot token only

In Discord app - Bot - Reset Token, copy the token. In Mage.Party Create App dialog, paste only that token and submit.

Mage.Party will auto-fetch and save Discord Application ID, Public Key, app metadata, and default endpoint/legal URLs.

What to expect: workspace is created and launch wizard opens automatically.

Step 3 - Verify auto-configured Discord URLs

Mage.Party attempts to auto-set Discord Interactions Endpoint URL and linked roles URL during app creation.

Open Settings to confirm values. If your token was rotated or permissions changed, save token again to re-apply.

What to expect: Discord accepts the endpoint without verification error.

Step 4 - Invite bot to your server

In Mage.Party Settings, click Add Bot to a Server.

Choose a server where your account has Manage Server permission and approve.

What to expect: bot appears in your server member list.

Step 5 - Create your first command

Go to Commands, click Create Command, and start simple.

Suggested values: name ping, description Check if bot is online.

Open Flow Editor and run a draft test before publishing.

Step 6 - Create a scenario and run it

Go to Scenarios, target your command, and use a small JSON payload such as{"role":"admin","reason":"smoke-test"}.

Set expected status to SUCCESS and output text to a known keyword from your command response.

What to expect: passing scenario means your flow is ready to publish.

Step 7 - Publish and verify in Discord

Go to Publish, enter a short release summary, then publish.

In Discord, type /ping in your server.

What to expect: slash command appears and returns your flow response. Global command propagation can take time; add app variable DISCORD_DEV_GUILD_IDfor instant guild command sync.

Common issues and quick fixes

Endpoint verification fails: check that your URL is HTTPS and publicly reachable.

Command does not appear in Discord: publish again and wait briefly for sync.

Publish fails with unauthorized error: regenerate bot token in Discord and save it again in Mage.Party settings.

Scenario fails: open Flow Editor Run Draft result and update expected contains text.