> 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

Currents integration with Slack allows posting test results of your Playwright or Cypress tests directly into Slack channels, helping your team stay informed about test outcomes without leaving Slack.

There are two versions of Slack integration available:

{% hint style="info" %}
**Recommendation:** We recommend 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 (up to 10 channels per project)
* ✅ Run-level notifications with thread-based grouping
* ✅ Individual test failure notifications
* ✅ Advanced filtering by tags, branches, and commit messages
* ✅ Annotation-based mentions (users, groups, emails)
* ✅ UI-based mention rules configuration
* ✅ Improved security with OAuth 2.0

## [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 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://docs.currents.dev/resources/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.