Connect Discord (bot: DMs and server)

This channel connects a Discord bot to Omnifox so the interactions it receives — direct messages and slash commands within your server — land in the Inbox like any other conversation. Setup has two parts: an OAuth authorization to add the bot to your server, and a manual credentials step, since Discord doesn't hand those over through OAuth.

Requirements

• An application created at discord.com/developers
• Admin permissions on the Discord server you're adding the bot to
• That application's Bot Token, Application ID, and Public Key (Ed25519)

Steps to connect

1. In Omnifox, go to Channels → Connect New Channel, pick Discord, and click the OAuth connect button.
2. Choose the Discord server you want to add the bot to and authorize the requested permissions.
3. Discord sends you back to Omnifox with a notice: the bot is now on your server, but the channel still needs its credentials to activate.
4. In the Discord developer portal, go to your app → Bot → Reset Token, and copy the Bot Token.
5. Also copy the Application ID and, under General Information, the Public Key (hex).
6. Paste all three values into Omnifox and save to activate the channel.

Configuration

• Bot Token: authenticates the bot's outbound messages.
• Application ID: identifies your Discord application.
• Public Key (Ed25519, hex): verifies the signature on inbound interactions Discord sends to your webhook.

Example

A user sends your bot a DM asking about the status of a request. That interaction arrives in the Omnifox Inbox as a Discord conversation, ready for an agent to reply.

Tips

• The first request Discord sends your webhook is a verification PING; if the channel doesn't respond, Discord disables the integration.
• Guard the Bot Token carefully — if you regenerate it in Discord, update it in Omnifox too.

Troubleshooting

• The bot shows up on the server but no messages arrive: confirm you pasted the correct Bot Token, Application ID, and Public Key — all three are required to activate the channel.
• Interactions fail signature verification: check that the Public Key you copied belongs to the right app — each app has its own.