Overview

This page is dedicated to Discord bot setup and covers:

1. Deploying the Nimera Bot in cloud deploy dashboard.
2. Discord-side setup (application, intents, invite, server structure).
3. Nimera panel-side setup (Admin -> Discord Bot).

Prerequisites

• A running NimeraCP Panel deployment.
• Access to Nimera dashboard Deploy page.
• Access to Discord Developer Portal.
• Admin permissions in your target Discord server.

1) Deploy the Nimera Bot

1. Open dashboard Deploy page.
2. Click Deploy Bot.
3. Enter bot deployment name and confirm.
4. Wait for deployment status Running.

Bot env linkage

Cloud bot deployment is linked to your panel deployment and uses:

PANEL_BASE_URL=https://<your-panel-domain>.com
API_KEY=<same-as-panel-api-key>
OUTBOX_POLL_INTERVAL_MS=5000
MESSAGE_CACHE_TTL_MS=300000
PARTYKIT_HOST=ws.nimeracp.com

2) Discord side setup

2.1 Create application and bot

1. Create a new application in Discord Developer Portal.
2. Create the bot user inside the application.
3. Copy:
   • Application ID
   • Bot Token

2.2 Enable required intents

Enable these intents on the bot page:

• Presence Intent
• Server Members Intent
• Message Content Intent

2.3 Invite bot to your server

Use OAuth2 URL generator with:

• Scopes: bot, applications.commands
• Permissions: admin for quick start (or equivalent granular permissions)

Invite URL template:

https://discord.com/api/oauth2/authorize?client_id=<your-application-id>&permissions=8&scope=bot%20applications.commands

2.4 Prepare channels/categories/roles

Create/select:

• Ticket panel channel
• Staff queue channel
• Open tickets category
• Closed tickets category (optional)
• Support staff roles

3) Nimera panel side setup

Open Admin -> Discord Bot in your panel.

3.1 Bridge Status

Configure:

• Enable bot integration
• Bot token
• Application ID
• Guild ID

Then click Load Discord Resources.

3.2 Discord Targets

Select targets:

• Ticket panel channel
• Staff queue channel
• Open tickets category
• Closed tickets category (optional)
• Support roles

Click Save.

3.3 Deploy ticket panel message

In Deploy Metadata, click Send Panel.

This posts (or refreshes) the ticket-entry panel message in Discord.

4) Verification checklist

• Bot deployment is Running.
• Bot is invited to the correct Discord server.
• Discord resources load successfully in panel.
• Ticket panel message is visible in configured channel.
• Test ticket creation syncs between Discord and panel.

Troubleshooting

"Deploy Panel first before deploying a bot"

Create and run panel deployment first, then deploy bot.

Discord resources load failed

Verify bot token, guild ID, bot invite, and enabled intents.

Send Panel failed

Verify ticket panel channel exists and at least one active ticket category is configured.

Custom domain options on bot

Bot deployments intentionally do not use custom domains.