qaemdev

Set up Deckord

Register a Discord application and connect it to Deckord so your Stream Deck keys and dials control the Discord desktop app.

Updated 9 Sept 2026

Discord requires every app that controls it to register itself once. You'll create a free application in Discord's Developer Portal, copy two values from it, and paste them into Stream Deck.

Before you start

Deckord shows as Disconnected until you finish this setup. You only do it once.

Setup

Create a Discord application

Open the Discord Developer Portal and sign in with the Discord account you normally use.

  1. Click New Application in the top-right corner.
  2. Name it Deckord, agree to the terms, then click Create.

Keep this tab open. You'll use it for the next two steps.

Add the redirect URL

This is the redirect address you'll add:

http://localhost:57116
  1. Click OAuth2 in the left sidebar.
  2. Under Redirects, click Add Redirect and paste the address above.
  3. Scroll down and click the green Save Changes button.

Copy your Client ID and Client Secret

  1. Go back to OAuth2 in the left sidebar.
  2. Click Copy under Client ID.
  3. Under Client Secret, click Reset Secret if none is shown, then click Copy.

Connect in Stream Deck

Make sure Discord is running, then switch to the Stream Deck app.

  1. Drag any Deckord action onto an empty key. Mute is a good first one.
  2. In the settings panel below, expand DISCORD CONNECTION.
  3. Paste your Client ID and Client Secret into the two fields.
  4. Click Authorize Discord, then click Authorize in the Discord window that pops up.

Letting someone else use your application

This part is optional. You don't need it for yourself: you created the application, so Discord already lets your own account authorize it, with nothing to accept and no invite to send.

It only matters if you give your Client ID and Client Secret to someone else, such as a second PC signed in to a different Discord account, or a friend you're setting up. Discord won't show them the authorization window until you add them as a tester:

  1. Open your application in the Developer Portal and click App Testers in the left sidebar.
  2. Click Add Tester, type their Discord username, and confirm.
  3. They open Discord and accept the invite. It must say Accepted, not Pending.

A simpler alternative is to have them follow this guide and create their own application. It takes the same five minutes, and nobody has to share a Client Secret.

Troubleshooting

The Authorize window never appeared

  • The Discord desktop app isn't running. Open it, log in, and click Authorize Discord again.
  • You're using someone else's Client ID and Secret, and they haven't added you under App Testers (see above). If you made the application yourself, this can't be the cause.
  • The window opened behind another window. Check your taskbar.
  • Discord is running as administrator and Stream Deck isn't, or the other way round. Run both the same way.

"Invalid OAuth2 redirect_uri"

The redirect saved in Discord doesn't match. It must be exactly http://localhost:57116: no https, no missing port, no trailing slash. Fix it, then click Save Changes at the bottom of the Discord page, which is easy to miss.

It says the client is invalid

Your Client ID or Secret was pasted wrong, or the secret was reset afterwards. Copy both again with the Copy buttons in the Developer Portal, check that no extra spaces came along, and paste them in again.

Keys show "Disconnected" after restarting my PC

Discord probably started more slowly than Stream Deck. Wait for Discord to finish loading, then press any Deckord key to reconnect.

Mute works, but channels and messages are empty

The authorization didn't cover everything Deckord needs, usually because it was granted once on an older version and Discord reused it. Open AUTHORIZED ACCOUNTS in the settings panel, remove the account, and click Authorize Discord again, approving the window that appears.

Privacy

Deckord talks to the Discord desktop app running on your own PC. Your Client ID, Client Secret and access token are stored locally in your Stream Deck settings. The only outbound request is the one-time token exchange with Discord's own servers during authorization.

Using the XENEON EDGE too?

The Deckord widget for the XENEON EDGE uses the same Discord application, so you can reuse the Client ID and Client Secret you just created. See Set up the Deckord widget.