A Discord connection is one of two kinds. A webhook URL posts to the one channel it was made in — quick to set up, and all most alerts need. A bot token posts to any channel your bot can see in the servers it has joined, and can also add reactions and start threads.

Who can do this

Workspace Admins and Editors, on any plan — Discord is not a premium connection. Viewers see the connection but cannot add or change it.

On Discord's side: for a webhook, someone with Manage Webhooks in the channel. For a bot, someone with Manage Server in the server it joins.

Webhook or bot

Webhook URL Bot token
Send a message, Send a file Yes, to its own channel Yes, to any channel the bot can post in
Choose the name and picture it posts under Yes No — it posts as the bot
Add a reaction, Create a thread No Yes
Set-up A minute, in the channel's settings An app in the Discord Developer Portal, invited to your server

Steps

A webhook URL

In Discord, make the webhook — here for the #alerts channel in the Consulace server:

  1. Beside #alerts, select the gear, Edit Channel.
  2. Open Integrations, then Webhooks, and select New Webhook.
  3. Select the new webhook. Give it a name — for example Consulace alerts — and, if you like, a picture. Check its channel is #alerts.
  4. Select Copy Webhook URL. It starts with https://discord.com/api/webhooks/.

A bot token

In the Discord Developer Portal, make the bot:

  1. Go to discord.com/developers/applications and sign in.
  2. Select New Application, name it — for example Consulace Bot — and create it.
  3. Open Bot. Select Reset Token, confirm, and copy the token. Discord shows it only this once. The bot needs none of the Privileged Gateway Intents.

Invite the bot to your server:

  1. Open OAuth2, then URL Generator.
  2. Under Scopes, tick bot.
  3. Under Bot Permissions, tick View Channels, Send Messages, Embed Links, Attach Files, Read Message History, Add Reactions, Create Public Threads and Send Messages in Threads.
  4. Copy the address at the bottom and open it in your browser.
  5. Choose the server — Consulace — and select Authorise. The bot appears in the server's member list.

In Bizomate

  1. Select Connections in the bar at the top, then + Add connection.

  2. Under Communication, select Discord. It reads "Stored credential", and says Fill in one of the two.

  3. In Connection name, type a name — for example Consulace Discord.

  4. Paste one of them:

    • the webhook's address in Webhook URL (optional) — To post to one channel: the channel's settings › Integrations › Webhooks › Copy Webhook URL.
    • or the token in Or a bot token (optional) — To post anywhere the bot is, react and start threads: Discord Developer Portal › your app › Bot › Reset Token. Invite the bot to your server first.

    Both are hidden as you type. If you fill in both, the bot token is used.

  5. Leave Test the connection before saving ticked. Bizomate asks Discord for the webhook or the bot before keeping it.

  6. Select Save connection. The button reads Testing, then the dialog closes.

The toast "Connection added" says "“Consulace Discord” is ready. Every workflow in this workspace can use it."

What happens next

  • Discord steps list it under Connection: Send a message, Send a file, Add a reaction and Create a thread.
  • Test in the connection's panel answers with what it reached — "Reached the webhook Consulace alerts · Discord", or "Reached Consulace Bot · Discord bot".
  • With a bot, the steps' Channel list shows the text and announcement channels in every server the bot has joined, such as #alerts · Consulace.
  • With a webhook, leave Channel empty — it posts to its own channel.

Good to know

  • To post to another channel with a webhook, make a webhook in that channel and add it as a second connection.
  • A bot only sees what its role lets it. In a private channel, or one with its own permissions, give the bot's role View Channel and Send Messages there.
  • A new token or webhook. Resetting the bot's token, or deleting the webhook, stops the connection. In Bizomate, open the connection's panel, select Revoke and Revoke connection, then Reconnect, paste the new one and select Reconnect. With Test the connection before saving ticked, Reconnect tries it first and changes nothing if Discord refuses it.
  • Anyone with the webhook URL can post to that channel. Keep it like a password.

If something goes wrong

What you see Why What to do
"Fill in one of them." Both boxes are empty. Paste a webhook URL or a bot token.
Discord refused it — "The webhook URL is not a Discord webhook — it starts https://discord.com/api/webhooks/. Copy it again from the channel's Integrations. Nothing was saved." The address is not a Discord webhook's. Select Copy Webhook URL in Discord again.
Discord refused it — "Discord refused: Unknown Webhook. Nothing was saved." The webhook was deleted, or the address is cut short. Copy it again, or make a new webhook.
Discord refused it — "Discord refused: Invalid Webhook Token. Check the connection's details on Connections. Nothing was saved." The end of the webhook URL is wrong or cut short. Select Copy Webhook URL in Discord again.
Discord refused it — "Discord refused: 401: Unauthorized. Check the connection's details on Connections. Nothing was saved." The bot token is wrong, or was reset. Reset the token in the Developer Portal and paste the new one.
"The Discord connection has neither a webhook URL nor a bot token. Reconnect it on Connections." (in a run) The connection's details are incomplete. Revoke it and Reconnect with one of them filled in.
"Could not reach Discord: …" or "Discord did not answer within 30 seconds." Discord could not be reached. Try again in a few minutes.