> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sndbox.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack Webhook

> Send an incoming webhook message. Exact configuration, ports, placement, and execution behavior.

**Node type:** `slack_webhook` · **Version:** `1` · **Category:** Communication

Send an incoming webhook message. This node can change external state or produce an external side effect.

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

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

## Workflow JSON

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

```json title="Default node configuration" theme={"system"}
{
  "type": "slack_webhook",
  "version": 1,
  "configuration": {
    "credentialId": "",
    "content": ""
  }
}
```

Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See [Variables and data mapping](/workflows/variables-and-data).

## Inputs

This node has no typed ports in this direction.

## Outputs

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

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