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

# Slack

Integrating Slack with Currents dashboard for test notifications

Currents integration with Slack allows posting test results directly into Slack channels, helping teams stay informed about test outcomes without leaving Slack.

There are two versions of Slack integration available:

{% hint style="info" %}
**Recommendation:** Currents recommends using the Slack App integration due to its advanced features and improved security model.
{% endhint %}

## [Slack App](/resources/integrations/slack/slack-app.md) Integration (Recommended)

The Slack App integration provides a rich, feature-complete experience for test notifications:

* ✅ Organization-level installation with per-project configuration
* ✅ Multiple destinations (the dashboard shows the organization's limit; the default is 10)
* ✅ Run-level notifications with thread-based grouping
* ✅ Individual failed or flaky test notifications
* ✅ Fix with AI from failed-test messages
* ✅ Run attachment colors for in-progress, timed-out, success, error, and cancelled states
* ✅ Live updates to the groups table on threaded run notifications
* ✅ Advanced filtering by tags, branches, and commit messages
* ✅ Annotation-based mentions (users, groups, emails)
* ✅ UI-based mention rules configuration
* ✅ Scheduled [Automated Reports](/dashboard/automated-reports.md) to a Slack channel (Block Kit summaries with dashboard links)
* ✅ Improved security with OAuth 2.0

The Slack App also delivers independently configured [Action lifecycle notifications](/guides/currents-actions/lifecycle-notifications.md) for actions that are created, disabled, re-enabled, archived, expiring, or expired. Connecting Slack under **Integrations** does not enable these notifications; Action notifications are configured under **Actions > Settings**.

Scheduled automated reports are configured per report on the project **Reports** page; see [Automated Reports to Slack](/resources/integrations/slack/slack-app.md#automated-reports-to-slack).

## [Slack Webhook](/resources/integrations/slack/slack-webhook.md) Integration (Legacy)

The webhook-based integration provides basic notification functionality:

* ✅ Simple setup with Incoming Webhooks
* ✅ Run start, finish, timeout, and cancel notifications
* ✅ Branch name filtering
* ✅ Tag-based filtering
* ❌ No individual test notifications
* ❌ No annotation-based mentions
* ❌ Limited to single channel per integration


---

# 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.currents.dev/resources/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 `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.