Discord — how to connect

Posts text messages (up to 2 000 characters) to a single Discord channel. Connect with either an Incoming Webhook URL (simplest — Channel Settings → Integrations → Webhooks) or a Bot token plus a Channel ID for edit/delete support. Nothing to configure here — paste the webhook URL or bot token when you add the channel.

Discord connects one of two ways: a simple per-channel Incoming Webhook URL (recommended), or a Bot token + Channel ID for edit/delete support. Pick one path below.

Before you start

Ability to manage the target Discord server/channel (Manage Webhooks permission or admin) to create an Incoming Webhook via Channel Settings → Integrations → Webhooks.
For the Bot token option: a Discord application + bot created in the Developer Portal, already invited to the server with an OAuth2 URL that included the `bot` scope and Send Messages permission.
For the Bot token option: Developer Mode enabled (User Settings → Advanced) so you can copy the numeric Channel ID via right-click → Copy Channel ID.
The credential in hand before starting — either the full Webhook URL (https://discord.com/api/webhooks/{id}/{token}) or the Bot Token — since connecting validates it immediately with a live Discord API call.

Step by step

1
Option A (simplest): create an Incoming Webhook
In Discord, open the target channel's Settings → Integrations → Webhooks → New Webhook, then click Copy Webhook URL.
Open
2
Paste the webhook URL
Paste the copied URL (format https://discord.com/api/webhooks/{id}/{token}) into the "Incoming Webhook URL" field here and leave the bot fields blank.
3
Option B (more capable): register an app and create a bot
Go to the Discord Developer Portal, click New Application, name it, then open the Bot tab and click Reset Token to reveal the bot token.
Open
4
Invite the bot to your server
On the app's Installation page, choose Discord Provided Link, add the bot scope, grant Send Messages permission, then open the generated install link and add the bot to your server.
Open
5
Get the target Channel ID
In Discord, enable User Settings → Advanced → Developer Mode, then right-click the channel and choose Copy Channel ID.
6
Paste the bot token and Channel ID
Paste the bot token into the "Bot token" field and the copied ID into "Channel ID (for bot token)" here, leaving the Webhook URL field blank.

Paste when you connect

Incoming Webhook URLsecret
Option A (simplest): channel → Settings → Integrations → Webhooks. Leave the bot fields blank.
Bot tokensecret
Option B (more capable): Developer Portal → your app → Bot → Token. Invite the bot to the server with Send Messages. Requires a Channel ID below.
Channel ID (for bot token)
Discord: User Settings → Advanced → Developer Mode on, then right-click the channel → Copy Channel ID.

Good to know

Fill only one variant: Webhook URL alone, or Bot token + Channel ID together — mixing both is unnecessary and the app treats a present bot token as the active path.
The webhook URL itself is the full secret credential; anyone with it can post to that channel, so treat it like a password.
A webhook is bound to a single channel (one webhook = one 'account' in this app); to post to another channel, create another webhook there.
The bot token path requires the bot to actually be invited into the server (via the Installation/OAuth2 install link) with Send Messages permission, or posts will fail with a 403/missing-access error even though the token itself is valid.
Copying a Channel ID requires Developer Mode to be enabled first (User Settings → Advanced → Developer Mode).
Messages are capped at 2000 characters and media/embeds are not sent by this integration — text only.

Troubleshooting

Connect fails with 'Discord webhook check failed: 401' or '404'.: The webhook was deleted or its token regenerated, or the URL was mistyped/truncated. Generate a fresh webhook URL from Channel Settings → Integrations → Webhooks and paste the full URL exactly.
Bot token connects fine but publishing fails with 'Discord 403: Missing Permissions' (code 50013).: The bot lacks Send Messages permission in that specific channel — server-level roles and per-channel overwrites are separate. Also confirm the bot was originally invited with the correct OAuth2 scopes/permissions, since scope gaps at invite time can't be fixed later by editing roles.
Connecting with a bot token throws 'A Channel ID is required when using a bot token'.: The bot-token path needs both the token and a Channel ID. Enable Developer Mode and right-click the target channel → Copy Channel ID, then paste it into the Channel ID field.
Publishing intermittently fails with 429 during bursts of scheduled posts.: Discord allows roughly 5 requests per 2 seconds per webhook/channel. Space out sends or back off using the returned retry_after value — repeated 429s can trigger a longer temporary IP-level block.

Discord developer docs

Discord — how to connect

Before you start

Ability to manage the target Discord server/channel (Manage Webhooks permission or admin) to create an Incoming Webhook via Channel Settings → Integrations → Webhooks.

For the Bot token option: a Discord application + bot created in the Developer Portal, already invited to the server with an OAuth2 URL that included the `bot` scope and Send Messages permission.

For the Bot token option: Developer Mode enabled (User Settings → Advanced) so you can copy the numeric Channel ID via right-click → Copy Channel ID.

The credential in hand before starting — either the full Webhook URL (https://discord.com/api/webhooks/{id}/{token}) or the Bot Token — since connecting validates it immediately with a live Discord API call.

Step by step

Option A (simplest): create an Incoming Webhook

In Discord, open the target channel's Settings → Integrations → Webhooks → New Webhook, then click Copy Webhook URL.

Open

Paste the webhook URL

Paste the copied URL (format https://discord.com/api/webhooks/{id}/{token}) into the "Incoming Webhook URL" field here and leave the bot fields blank.

Option B (more capable): register an app and create a bot

Go to the Discord Developer Portal, click New Application, name it, then open the Bot tab and click Reset Token to reveal the bot token.

Open

Invite the bot to your server

On the app's Installation page, choose Discord Provided Link, add the bot scope, grant Send Messages permission, then open the generated install link and add the bot to your server.

Open

Get the target Channel ID

In Discord, enable User Settings → Advanced → Developer Mode, then right-click the channel and choose Copy Channel ID.

Paste the bot token and Channel ID

Paste the bot token into the "Bot token" field and the copied ID into "Channel ID (for bot token)" here, leaving the Webhook URL field blank.

Paste when you connect

Incoming Webhook URLsecret

Option A (simplest): channel → Settings → Integrations → Webhooks. Leave the bot fields blank.

Bot tokensecret

Option B (more capable): Developer Portal → your app → Bot → Token. Invite the bot to the server with Send Messages. Requires a Channel ID below.

Channel ID (for bot token)

Discord: User Settings → Advanced → Developer Mode on, then right-click the channel → Copy Channel ID.

Good to know

Fill only one variant: Webhook URL alone, or Bot token + Channel ID together — mixing both is unnecessary and the app treats a present bot token as the active path.

The webhook URL itself is the full secret credential; anyone with it can post to that channel, so treat it like a password.

A webhook is bound to a single channel (one webhook = one 'account' in this app); to post to another channel, create another webhook there.

The bot token path requires the bot to actually be invited into the server (via the Installation/OAuth2 install link) with Send Messages permission, or posts will fail with a 403/missing-access error even though the token itself is valid.

Copying a Channel ID requires Developer Mode to be enabled first (User Settings → Advanced → Developer Mode).

Messages are capped at 2000 characters and media/embeds are not sent by this integration — text only.

Troubleshooting

Connect fails with 'Discord webhook check failed: 401' or '404'.

The webhook was deleted or its token regenerated, or the URL was mistyped/truncated. Generate a fresh webhook URL from Channel Settings → Integrations → Webhooks and paste the full URL exactly.

Bot token connects fine but publishing fails with 'Discord 403: Missing Permissions' (code 50013).

The bot lacks Send Messages permission in that specific channel — server-level roles and per-channel overwrites are separate. Also confirm the bot was originally invited with the correct OAuth2 scopes/permissions, since scope gaps at invite time can't be fixed later by editing roles.

Connecting with a bot token throws 'A Channel ID is required when using a bot token'.

The bot-token path needs both the token and a Channel ID. Enable Developer Mode and right-click the target channel → Copy Channel ID, then paste it into the Channel ID field.

Publishing intermittently fails with 429 during bursts of scheduled posts.

Discord allows roughly 5 requests per 2 seconds per webhook/channel. Space out sends or back off using the returned retry_after value — repeated 429s can trigger a longer temporary IP-level block.