Discord Nodes
Post messages and rich embeds to Discord channels from a pipeline, by webhook or bot.
- Operations
- Send Message
Discord is a chat platform many maintenance, operations and engineering teams use for alerts. The Discord node posts a message to a channel through the connection's incoming webhook or bot. See the Discord connection guide for setting up either mode.
Configuration Quick Reference
| Field | What you choose | Details |
|---|---|---|
| Parameters | Connection, Function, Function Parameters, Timeout Override | Select the connection profile, function, configure function parameters with expression support, and optionally override timeout. |
| Settings | Description, Timeout (seconds), Retry on Timeout, Retry on Fail, On Error | Node description, maximum execution time, retry behavior on timeout or failure, and error handling strategy. All execution settings default to pipeline-level values. |
Discord Send Message Node
Discord Send Message Node
Post a message, with optional embeds, to a Discord channel. A webhook connection posts to the webhook's own channel; a bot connection posts to the channel the function names.
Supported Function Types:
| Function Name | Purpose | Common Use Cases |
|---|---|---|
| Send Message | Post text and embeds to a Discord channel | Line-stop alerts, shift summaries, batch completion notices, quality holds |
Mentions are off unless the function allows them: @everyone, @here, role and user mentions in the text are shown but ping nobody, so a value that happens to contain @everyone cannot page a whole server.
The channel list you see while building a Send Message function in bot mode comes from the connection's channel picker. It is not a function you can save, so no node returns it.
Retries. A send that Discord refused (an unknown channel, a missing permission, a message it rejected) fails with a permanent error and is not worth retrying. A send whose outcome is unknown (a timeout, a dropped connection, a 5xx or a rate limit) may already be posted, so Retry on Fail can post it twice.
Output
The Discord node delivers its data under result, and execution facts (success, functionId, durationMs, timestamp) under _metadata:
| Expression | Description |
|---|---|
$node["Name"].result.messageId | The id Discord gave the posted message |
$node["Name"].result.channelId | The channel the message landed in; for a webhook, the webhook's own channel |
$node["Name"].result.createdAt | When Discord recorded the message, UTC RFC 3339; present only when Discord's timestamp parsed |
$node["Name"]._metadata.method, $node["Name"]._metadata.connectionId, $node["Name"]._metadata.protocol, $node["Name"]._metadata.authType, $node["Name"]._metadata.message | The call's own facts: the operation, the connection it ran over, discord, webhook or bot, and a one-line note about what happened |