Discord Webhook

Node type: discord_webhook · Version: 1 · Category: Communication Send a webhook message. sndbox classifies this node as side-effecting, so tests or automatic runs can require additional confirmation and permission review.

When to use this node

Send a concise alert to a Discord channel through a stored webhook.
Post mapped workflow results without placing the webhook URL in workflow data.

Example: Post a service alert

Send a mapped HTTP status with a recognizable bot name.

Example settings

{
  "credentialId": "discord-ops",
  "content": "Checkout health returned {{nodes.request.output.status}}.",
  "username": "sndbox monitor",
  "avatarUrl": ""
}

This shows the important settings, not a complete exported node. Connection and profile IDs are illustrative; select the real resource in the inspector.

Create the Discord webhook connection.
Map concise, non-sensitive content.
Branch so alerts are posted only for the intended condition.

Configuration

Field	Type	Default	What it controls
`credentialId`	string	`""`	Reference to a connection stored in the operating-system credential vault.
`content`	string	`""`	Literal or mapped content. For parser nodes, mapped content takes precedence over the optional file.
`username`	string	`""`	Optional Discord webhook username override.
`avatarUrl`	string	`""`	Optional Discord webhook avatar URL.

The webhook URL is resolved inside the Rust host and never enters workflow data or logs.

Workflow JSON

The editor stores this node with the following implemented default configuration:

Default node configuration

{
  "type": "discord_webhook",
  "version": 1,
  "configuration": {
    "credentialId": "",
    "content": "",
    "username": "",
    "avatarUrl": ""
  }
}

Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

Inputs

This node has no typed ports in this direction.

Outputs

Port	Type	Required	Description
`result`	`any`	No	Result

Execution behavior

The webhook URL remains in the host vault; the node sends content through the secure integration host.
username and avatarUrl override presentation only for this message when Discord permits it.
The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

Common issues

Discord rate limits and content limits still apply.
Avoid posting secrets or raw customer data to a broad channel.

Where it can run

Desktop local runner
Paired self-hosted runner
Hosted runner

Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.

Node reference

Triggers

Logic

Data

Network

Browser

Communication

System

When to use this node

Example: Post a service alert

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Post a service alert

​Configuration

​Workflow JSON

​Inputs

​Outputs

​Execution behavior

​Common issues

​Where it can run

​Test and inspect

​Related guides

When to use this node

Example: Post a service alert

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides