Connect Discord

≈ 4 min Extension Bearer Token

The secret depends on the Resource you use. Create one credential for each and pick the right one on the node.

Before you start

• Manage Webhooks permission on the channel (webhook), or Manage Server to add a bot.
• The AWFlow browser extension. These steps run in the extension (the web app hands them to it).

Used by

• Discord

Pick a method

Method	Use it when
Webhook URL Recommended	Webhook › Send: post messages and embeds to one channel. Nothing to install.
Bot token	Channel and Message operations: get or list channels, read messages, react.

Set it up

Webhook URL (recommended)

1. Create the webhook. In Discord, open the channel’s Edit Channel › Integrations › Webhooks, click New Webhook and Copy Webhook URL.

2. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Discord in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Discord Under Integration App / Service, pick Discord. There is no Auth Type menu: Discord uses a Bearer Token.
   2. 2 Step 2:Name it For example Discord – #alerts webhook. A Description is optional.
   3. 3 Step 3:Paste the webhook URL Paste the full webhook URL into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Discord; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Webhook › Send with the content Hello from AWFlow: the message appears in the channel.

Bot token

1. Create a bot. In the Discord Developer Portal, click New Application, open Bot and click Reset Token. Copy the token.

2. Allow message text if you read messages: on the Bot page, turn on Message Content Intent.

3. Invite the bot. In OAuth2 › URL Generator, tick bot, then View Channels, Read Message History and Add Reactions. Open the generated URL and add the bot to your server.

4. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Discord in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Discord Under Integration App / Service, pick Discord. There is no Auth Type menu: Discord uses a Bearer Token.
   2. 2 Step 2:Name it For example Discord – reader bot. A Description is optional.
   3. 3 Step 3:Paste the token Paste the bot token into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Discord; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Channel › List with your server’s ID: its channels come back.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to discord.com. AWFlow’s servers never relay the call.

Privacy & your data →

Common issues

• “Unknown Webhook”. The webhook URL is wrong or the webhook was deleted. Create a new one and update the credential.
• “401: Unauthorized” on Channel or Message. The credential holds a webhook URL, or the bot token was reset. Use a bot token credential.
• “Missing Access”. The bot isn’t in that server, or its role can’t see the channel.
• Messages come back with empty text. Turn on Message Content Intent for the bot.
• The run is blocked in the web app. Discord runs through the browser extension. Install the extension and allow Discord for this workflow when asked, or run the workflow from the extension. See Extension-only integrations in the web app.

Related

Discord node

All connections

Create and manage credentials

Privacy & your data