Skip to main content

What this deployment supports

Bothive connects Discord through its HTTP Interactions endpoint. Your agent receives signed slash-command interactions without maintaining a persistent gateway connection.
This is command-first Discord support. It is ideal for /ask, FAQ, community support, and internal server assistants. It does not read every ordinary server message through the Discord Gateway.

Before you start

You need a Discord application and these values from the Discord Developer Portal: Never share the bot token. Bothive uses the public key only to verify Discord’s signed interaction requests.

Deploy to Discord

1

Create a Discord application

Open the Discord Developer Portal, select New Application, give it a name, and create a bot under Bot.
2

Add a Discord channel in Bothive

Open your agent in Bothive, then Channels > Discord. Enter the Bot Token, Application ID, and Public Key. Add a Server ID only if you want to restrict the agent to one server.
3

Set the Interactions Endpoint URL

Back in Discord, open General Information and set Interactions Endpoint URL to the URL shown after saving the Bothive channel. On the standard production domain it is:
Discord immediately sends a signed PING. Bothive answers it and verifies the request signature with the Public Key you provided. Do not use a URL from a local development server.
4

Install the app in a server

In Installation, enable Guild Install and include the applications.commands scope. Include the bot scope if you also want a bot user in the server. Install the app into a test server first.
5

Create and test a slash command

Create a command such as /ask in the Developer Portal or with Discord’s application-command API. Send a real question through that command, then inspect the run in Bothive Observability.
Start with a single /ask command. Add more commands only when a distinct workflow needs a clearer entry point.

Security and testing

Troubleshooting

Recopy the Public Key and ensure the URL uses your deployed Bothive domain. Discord validates the endpoint with a signed PING request, so it must be publicly reachable.
Confirm the application is installed with applications.commands. Use a guild-scoped command while testing; Discord recommends guild commands for fast iteration.
This deployment handles Discord interactions such as slash commands. Use /ask rather than expecting it to read every message in a channel.

Next reads

Deploy to Channels

Slack Bots

Read Your First Trace