> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/account-intelligence/workflows/nodes/destinations/slack.md).
# Slack
The **Slack** node posts account or contact summaries to a Slack channel of your choice as your workflow runs. Use it for real-time alerts on high-intent activity, team handoffs, and sales-room collaboration.
### What it does
* **Enriches every message** with company details such as revenue, headcount, industry, and owner.
* **Groups contacts by company**, so one account doesn't flood the channel with separate posts.
* **Adds the company logo and a *****See details***** button** that deep-links back to HockeyStack for quick follow-up.
* **Works for both company-level and individual-level workflows.**
* **Includes safeguards** to keep channel noise down.
* **Supports custom messages,** write your own text, @mention teammates, and insert variables from the record.
### Configuration
| Setting | Required | Description |
| -------------- | -------- | ---------------------------------------------------------------------------------------- |
| Channel Name | Yes | The Slack channel the node posts to. |
| Custom Message | No | Your own message template. Leave it empty to use the default HockeyStack summary format. |
### Customizing the message
By default, the Slack node sends HockeyStack's standard summary. If you want the alert to read differently, for example, to tag the account owner or show a specific field, write a custom message.
In a custom message you can:
1. **Write your own text.** Explain why the alert fired and what the team should do next.
2. **@mention users.** Tag the right people (such as an AE or the SDR team) so they get notified in Slack.
3. **Insert variables.** Pull values from the company or contact into the message, such as **Number of Employees**, **Industry**, or **Company Owner**. Each variable fills in with the value for that specific record when the message is sent.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.hockeystack.com/account-intelligence/workflows/nodes/destinations/slack.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
