> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/integrations-and-data-ingestion/how-to-connect-workflows-with/slack.md).

# Slack

### Overview

Workflows use Slack to deliver what they find and to ask for a decision. A workflow can post a report in a channel and, when it proposes something that needs a person's approval (for example creating a new card), show **Approve** and **Dismiss** buttons.

You connect Slack once by installing the Birdie app in your workspace. You do **not** create your own Slack app and you do not copy any token.

### What Birdie will do

* Post messages in the channels you choose.
* Reply in the thread of its own messages to confirm what happened.
* Read replies and reactions on its own messages, so approvals and follow-ups work.

Birdie only posts in channels it has been invited to. It does not read other conversations.

### Requirements

* Permission to install apps in your Slack workspace. If your workspace requires app approval, a Slack admin must approve the Birdie app.
* The channel where reports should arrive (you will need its **channel ID**, see below).

### Setup

{% stepper %}
{% step %}

### Install the Birdie app

* In Birdie, create or edit the workflow and, in the Slack credential field, choose **Connect Slack**.
* Slack opens a consent screen. Choose your workspace and review the permissions.
* Click **Allow**.

If your workspace requires approval, Slack sends the request to your admins. Once approved, repeat this step.
{% endstep %}

{% step %}

### Invite the app to the channel

In the channel where reports should arrive, type:

```
/invite @Birdie
```

For a private channel, an existing member must do this. Birdie cannot post in a channel it has not been invited to.
{% endstep %}

{% step %}

### Find the channel ID

* Open the channel and click its name at the top.
* Scroll to the bottom of the **About** tab and copy the **Channel ID** (it starts with `C`, for example `C0ABC1234`).
* Enter it in the workflow's **Slack channel ID** field.
  {% endstep %}
  {% endstepper %}

### Permissions Birdie requests

| Permission                           | Why                                                    |
| ------------------------------------ | ------------------------------------------------------ |
| `chat:write`                         | Post and reply in channels it is invited to            |
| `channels:read`, `groups:read`       | Recognise the channel it posts in (public and private) |
| `channels:history`, `groups:history` | Read replies to its own messages                       |
| `reactions:read`                     | Notice reactions on its own messages                   |

### Revoke or rotate

* To stop Birdie posting, remove the app from the channel (`/remove @Birdie`) or uninstall it from **Slack → Administration → Manage apps**.
* To reconnect, repeat the first step. Existing workflows pick up the new connection when they are edited and saved.

{% hint style="info" %}
Slack as a **data source** (importing conversations into Birdie) is a different integration with its own setup: see [Slack](https://ask.birdie.ai/integrations-and-data-ingestion/how-to-integrate-with/slack.md).
{% endhint %}


---

# 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://ask.birdie.ai/integrations-and-data-ingestion/how-to-connect-workflows-with/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 `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.
