---
title: "How do I use the Slack Notification node in Orchestrator?"
source_url: https://help.chilipiper.com/hc/en-us/articles/53533252482067-How-do-I-use-the-Slack-Notification-node-in-Orchestrator
article_id: 53533252482067
updated_at: 2026-07-24T18:56:01Z
content_hash: 972beadf
---

## Who can use this feature?

Available on Orchestrator

Available to Admins  Workspace Managers

[Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub)

In this article, we will learn more about the Slack node and how to set it up in Orchestrator, ensuring your Flows keep the right people informed the moment something happens.

#### Table of Contents

- [What Is the Slack Node?](#what-is-the-slack-node)

- [Who It Sends To](#who-it-sends-to)

- [Writing the Message](#writing-the-message)

- [Good to Know](#good-to-know)

## What Is the Slack Node?

It sends a Slack message the instant something happens in a Flow. It is how reps and leadership stay in the loop without anyone refreshing a dashboard.

For example, an Enterprise prospect abandons a form, and the account owner gets a Slack ping while the intent is still warm.

![](https://help.chilipiper.com/hc/article_attachments/53533810818067)
## Who It Sends To

Two are the options you can choose from:

- **Channel:** post to one or more Slack channels, such as #sales-leadership. Good for team visibility.Ensure **chilibot** is invited to the channel beforehand.

- **User:**

**Dynamic receiver:** a variable from the Flow that is a Chili Piper user ID, such as Host.id. Most often, this is Host, Booker, or Assignee, or the CRM Owner from a Matching node;

- **Specific receiver:** a fixed user chosen directly.

__

**Common Use Cases** 

- Chain two Slack nodes, one to the CRM Owner and one to a leadership channel, so the right person acts, and leadership still has visibility.

- After a Matching or HTTP node, add a Slack node to the Flow owner or builder, so they can debug it.

## Writing the Message

Write the message with variables mixed right into the text, so it carries real context.

**Example:** "Form abandoned alert! `{{Guest Email}}` from `{{Account Name}}` abandoned the form before submitting."

**💡 Tip:** The best alerts say what happened and what has already been done, like "We added them to your Salesloft cadence." That turns a notification into reassurance instead of another task.

__

## Good to Know

- Slack must be connected in Chili Piper; to message the owner, a Matching node is usually needed first to resolve who that is;Slack can be connected in the Command Center [here](https://fire.chilipiper.com/fire/admin/integrations/built-in)

- If Slack is not connected, the node can still show as successful in Logs while no message went out; confirm the message arrived rather than trusting the Logs status alone.