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

# Slack

## Overview

The Slack StackPack allows you to receive event notifications in Slack channels. The StackPack installs a number of event handler functions that can be used when [adding an event handler](/5.1/use/events/manage-event-handlers.md#add-event-handler) to a view in StackState.

Slack is a [StackState core integration](/5.1/stackpacks/integrations/about_integrations.md#stackstate-core-integrations).

![Slack StackPack](/files/Bb5CmUclMk4L7BzyIGlj)

* Event handlers added to a StackState view run an event handler function in response to events that are generated in StackState.
* A Slack event handler function sends an alert to the specified Slack Webhook URL with details of the generated event.
* An alert appears in the Slack channel associated with the specified Slack Webhook.

![Slack alert](/files/we7kaHHC21rrWb8wUFkm)

## Setup

### Install

Install the Slack StackPack from the StackState UI **StackPacks** > **Integrations** screen. You don't need to enter any details.

### Configure

After the Slack StackPack has been installed, a Slack event handler function will be listed when you [add an event handler to a view](/5.1/use/events/manage-event-handlers.md#add-event-handler).

Note that you will need to [create a Slack Webhook (slack.com)](https://api.slack.com/messaging/webhooks).

### Upgrade

When a new version of the Slack StackPack is available in your instance of StackState, you will be prompted to upgrade in the StackState UI on the page **StackPacks** > **Integrations** > **Slack**.

{% hint style="success" %}
For an overview of recent StackPack updates, check the [StackPack versions](/5.1/setup/upgrade-stackstate/stackpack-versions.md) shipped with each StackState release.
{% endhint %}

## Integration details

### Data retrieved

The Slack integration is used to send event notifications to Slack. It doesn't retrieve any data from Slack.

## Uninstall

To uninstall the Slack StackPack, go to the StackState UI **StackPacks** > **Integrations** > **Slack** screen and click **UNINSTALL**.

{% hint style="info" %}
Before you uninstall the Slack StackPack, all event handlers that have been configured to use one of the Slack event handler functions installed by the StackPack must be deleted.
{% endhint %}

## Release notes

**Slack StackPack v0.0.7 (2021-12-10)**

* Improvement: Add description text to StackPack pages.

**Slack StackPack v0.0.6 (2021-08-24)**

* Improvement: Add related problems to view health handler

**Slack StackPack v0.0.5 (2021-08-23)**

* Improvement: Include contributing causes to the problem handler
* Improvement: Support for warnings when Problems are created, merged and resolved.

## See also

* [Manage event handlers](/5.1/use/events/manage-event-handlers.md)
* [Event notifications](/5.1/use/events/event-notifications.md)
* [Problem notifications](/5.1/use/problem-analysis/problem_notifications.md)
* [Event handler functions](/5.1/develop/developer-guides/custom-functions/event-handler-functions.md)
* [Create a Slack Webhook(slack.com)](https://api.slack.com/messaging/webhooks)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://archivedocs.stackstate.com/5.1/stackpacks/integrations/slack.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.