> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/~/revisions/ETrLpNk6KtHjyaVUTLoE/integrations/workflow-integrations/slack-app-with-bot-tokens.md).

# Slack App with Bot Tokens

{% hint style="info" %}
Adding a Slack App depends on your workspace’s approval settings. In some workspaces, any member can install apps, while in others only admins or owners can approve them. If approval is required, you’ll see a “**Request to install**” button and the request must be approved before the app is added.
{% endhint %}

### Adding the Slack App Integration

#### Create a Slack App

1. Go to [Slack API – Your Apps](https://api.slack.com/apps).
2. Click **Create New App** → choose **From Scratch**.
3. Give the app a name (e.g., g*roundcover Alerts*) and select your workspace.

#### Configure Permissions

1. In the left menu, go to **OAuth & Permissions**.
2. Under Scopes (Bot Token Scopes), add at least:
   1. *chat:write* - allows the app to post messages.
   2. (Optional) *chat:write.public* – required if the app should post to public channels it isn’t a member of.
3. Save your changes.

#### Install the App

1. In the same menu, scroll up and click **Install App to Workspace**.
2. Approve the requested permissions.
3. After installation, you’ll see an **OAuth Tokens for Your Workspace** section. Copy the **Bot User OAuth Token** (it begins with xoxb-). This is the token you’ll use in groundcover to send notifications.

#### Invite the App to Channels

For the app to post in a channel, it must be a member:

* In Slack, open the channel and run:

```
/invite @[your-app-name]
```

**Next step:** Once the app is installed, configure groundcover to use the bot token and channel IDs to send alerts dynamically via Slack’s chat.postMessage API. Create a webhook with the following attributes:

* Integration Name: slack-routing-endpoint (it can be any name)
* Webhook URL: <https://slack.com/api/chat.postMessage>
* Headers: Key: Authorization, Value: Bearer xoxb-\[your-bot-token-from-app]

You are now ready to use your Slack App integration with [a workflow](https://docs.groundcover.com/~/revisions/ETrLpNk6KtHjyaVUTLoE/use-groundcover/workflows/full-webhook-examples/slack-app-for-channel-routing)


---

# 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.groundcover.com/~/revisions/ETrLpNk6KtHjyaVUTLoE/integrations/workflow-integrations/slack-app-with-bot-tokens.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.