> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/slack.md).

# Slack

Connect a workspace Slack app to send workflow notifications and use supported channel actions.

## Connect

An admin opens **Settings → Integrations → Slack**, authorizes the correct Slack workspace and checks the displayed team name after returning to Distro.

Map member Slack identities in [Connected identities](/settings/identities.md) when a step needs a person or mention. A channel destination and a member identity are different values.

## Send a useful notification

Add a Slack message step after the decision it describes. Choose the supported channel or destination, then map the lead name, email, owner and a relevant record link.

Place assignment notifications after assignment succeeds. Place booking notifications on the **Booked** branch if they are intended to announce a confirmed meeting.

Channel creation and adding members are separate actions. Check the app's access to the destination, particularly for private channels.

## Check delivery

Simulation shows sample output. Verify a controlled live message in the destination channel and inspect the step result.

If delivery fails, check authorization, channel availability, app membership and mapped IDs. If a mention appears as text, review the member mapping rather than replacing it with a display name.

[Workspace alerts](/settings/workspace-alerts.md) controls operational failure notifications. It is separate from messages you place on the workflow canvas.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/integrations/slack.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.
