How to Connect Discord to Converge

Create the application in the Discord Developer Portal: click New Application, type a name, then click Create. The name shows on the bot's profile to anyone in your server, so pick something a customer would recognize — "Acme Support", not "test-bot-3".

You no longer add a bot user. Older walkthroughs tell you to open the Bot tab, click "Add Bot" and confirm with "Yes, do it!". That button is gone. Discord's quick-start now states that newly-created apps have a bot user enabled by default, so the Bot page is already populated when you land on it.

Copy the Application ID from the General Information page. Converge needs this value. It is public — it identifies your app, it does not authenticate it, and there is no harm in it appearing in a browser URL.

"Application ID" and "Client ID" are the same number. General Information calls it Application ID; the OAuth2 page calls it Client ID. If another guide asks for a Discord Client ID, paste the Application ID. Converge labels its field Application ID.

The bot token and the Message Content intent both live on the Bot page of your app's settings. You need the token to authenticate, and you need the intent toggle for Converge's connection to open at all.

Copying the bot token

On the Bot page, find the Token section, click Reset Token, then Copy. Discord shows a bot token exactly once — its own guide warns "you won't be able to view your token again unless you regenerate it". Put it in a password manager before you navigate away from the page.

Treat the token as a password: anyone holding it can send messages as your bot. Resetting it invalidates the previous one, so a reset performed after you connect stops message delivery until you paste the new value into Converge.

Why Message Content is required

Message Content is a privileged intent, so Discord makes you opt in before your app can request it. Scroll to Privileged Gateway Intents on the Bot page, switch on Message Content Intent, and save.

The usual explanation for this toggle is wrong. Discord's gateway documentation lists "content in DMs with the app" as an explicit exception — a bot reads DM text with or without the intent. Converge needs it for a different reason: Converge's Discord client requests MESSAGE_CONTENT when it identifies with the gateway, and passing a privileged intent you have not toggled makes Discord close the connection with code 4014. So the symptom of forgetting this toggle is not blank messages. It is a bot that never comes online.

Apps with fewer than 10,000 users can enable the intent themselves in the portal; above that threshold Discord requires a review before access continues.

Adding the bot to a server is mandatory, not optional. Discord only lets someone open a DM with a bot they already share a server with, so a customer who finds the bot's profile through a link and tries to message it gets Clyde's rejection instead: "Your message could not be delivered. This is usually because you don't share a server with the recipient or the recipient is only accepting direct messages from friends" (Discord Support).

The quickest invite link is the one Converge builds for you. Paste your Application ID into Converge's Discord panel and an Invite bot to your server link appears under the field. It points at https://discord.com/oauth2/authorize?client_id=<APPLICATION_ID>&scope=bot — the bot scope and no permissions, because receiving and sending DMs requires none. Open it, choose your server, click Authorize.

The Developer Portal builds the same URL under Installation, but there is little reason to assemble it by hand when the panel generates it for you.

Two settings can still block a DM after the bot is in the server. A member who turned off "Allow direct messages from server members" for that server cannot message the bot, and a member who has not completed the server's membership screening cannot either.

Customers reach you by clicking the bot in the member list and choosing Message. Every DM they send lands in your Converge inbox. Anything they post in an ordinary channel does not, because the bot subscribes to direct-message events only.

Open SettingsPlatformsDiscord in Converge, paste the two values, and click Enable. The panel holds exactly two fields — Application ID and Bot Token — and the token field has an eye icon if you want to confirm what you pasted.

The button says Enable, not Connect. Converge stores the credentials, opens a gateway session with Discord, and confirms with "Discord enabled". Disconnecting later is the Disable button in the same panel.

Only Owners and Admins see this screen. Agent accounts cannot manage platform connections and are refused by the integration endpoints.

Credentials lock while the integration is live. Editing the Application ID or Bot Token with Discord enabled is refused with "Disable integration before editing". Click Disable, change the value, then Enable again — rotating a token is three clicks rather than a rebuild from scratch.

If the connection attempt fails, Converge rolls the integration back to disabled instead of leaving it half-connected, and reports "Failed to connect to Discord".