Discord Embed

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

When to use this node

Post a structured Discord alert with a title, fields, color, and optional link or image.
Make monitoring results easier to scan than a plain webhook message.

Example: Post a structured deployment result

Send a green embed with the deployment status and revision.

Example settings

{
  "credentialId": "discord-ops",
  "content": "",
  "title": "Deployment complete",
  "description": "Production deployment succeeded.",
  "fields": [
    {
      "name": "Revision",
      "value": "{{trigger.revision}}",
      "inline": true
    }
  ],
  "color": 5793266,
  "link": "https://example.com/deployments",
  "image": ""
}

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

Use a decimal color value and short field names.
Map only fields suitable for the destination channel.
Test rendering with realistic lengths.

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.
`title`	string	`""`	Notification, message, or embed title.
`description`	string	`""`	Discord embed description.
`fields`	array	`[]`	Column mapping used for table extraction, or Discord embed field objects.
`color`	number	`5793266`	Discord embed color as a decimal integer.
`link`	string	`""`	Optional link for the Discord embed.
`image`	string	`""`	Optional image URL for the Discord embed.

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_embed",
  "version": 1,
  "configuration": {
    "credentialId": "",
    "content": "",
    "title": "",
    "description": "",
    "fields": [],
    "color": 5793266,
    "link": "",
    "image": ""
  }
}

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

description supplies the required embed content; content can add surrounding plain text.
The webhook credential remains in the vault and sending requires communication permission.
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 enforces per-field and total embed limits.
Remote image URLs disclose a fetch to their host and may fail if not publicly accessible.

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 structured deployment result

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

​When to use this node

​Example: Post a structured deployment result

​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 structured deployment result

Configuration

Workflow JSON

Inputs

Outputs

Execution behavior

Common issues

Where it can run

Test and inspect

Related guides