How do I use the Slack Notification node in Orchestrator?

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?
• Who It Sends To
• Writing the Message
• 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.

Who It Sends To

Two are two options you can chose from:

• Channel: post to one or more Slack channels, such as #sales-leadership. Good for team visibility;
• 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 

1. 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.
2. 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."

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