Skip to main content
Node type: slack_webhook · Version: 1 · Category: Communication Send an incoming 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

  • Post a plain alert or status update to a Slack incoming webhook.
  • Send mapped workflow results while keeping the webhook secret out of the graph.

​
Example: Notify the operations channel

Post a mapped status only from the failure branch of a health check.
Example settings
This shows the important settings, not a complete exported node. Connection and profile IDs are illustrative; select the real resource in the inspector.
  1. Create a Slack webhook connection.
  2. Connect the node only to the branch that should communicate.
  3. Keep the message concise and link to non-sensitive evidence when needed.

​
Configuration

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
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

​
Execution behavior

  • The incoming webhook URL is resolved inside the host and never becomes workflow data.
  • Sending is an external communication side effect governed by workflow permission review.
  • 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

  • Webhook destinations are fixed by their Slack configuration; confirm the selected connection points to the intended workspace and channel.
  • Rate limits or a revoked webhook cause a node failure that should not be retried without bounds.

​
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.