Create Webhook

discord.create_webhook
ActionChat & messagingconnection required

Calls the Discord API with the connection's credentials.

Create an incoming webhook on a channel.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Discord
Secret shape
the bot token (sent as "Authorization: Bot <token>") for every op except discord.execute_webhook, whose secret is the webhook URL
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
channel_id
Id of the Discord channel (right-click the channel → Copy Channel ID).
stringYes———
name
Webhook display name, 1-80 characters.
stringYes—1–80 characters—
reason
Why the change was made; recorded in the server's audit log.
stringNo—≤ 512 characters—

Output

One shape.

result

FieldTypeExample
id
Id of the webhook.
string—
type
Webhook type (1 incoming, 2 channel follower, 3 application).
number—
guild_id
Server the webhook posts into.
string—
channel_id
Channel the webhook posts into.
string—
name
Webhook display name.
string—
application_id
Application that owns the webhook, if any.
string—
{
  "application_id": "",
  "channel_id": "",
  "guild_id": "",
  "id": "",
  "name": "",
  "type": 0
}

Notes

  • Needs a Discord connection whose secret is the bot token.
  • Needs MANAGE_WEBHOOKS.
  • Discord refuses a name containing 'clyde' or 'discord' (either case).
  • The new webhook's token and URL are stripped from the output: they are credentials, and a run's step output is not a place to keep one. Read the URL in Discord and store it as a connection secret.

See Create Webhook run in a workflow.

In a technical demo we add the Discord connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.