> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Connect Slack so your team gets issue notifications with inline actions, chats with the Sazabi agent, and shares context without leaving Slack.

## Supported capabilities

Core integration

* **Core integration**: [Slack](https://docs.sazabi.com/catalogs/integrations/slack.md#core-integration) — Connect Slack so your team gets issue notifications with inline actions, chats with the Sazabi agent, and shares context without leaving Slack.

Each connection method has its own setup and permissions. Connecting one method does not enable the others.

## Core integration

## About

Connecting Slack brings Sazabi into the channels where your team already works. Slack is a **chat** integration and a shared [notification channel](https://docs.sazabi.com/guides/detect/notifications.md).

With Slack connected you can:

* Receive issue notifications as cards with inline **Resolve**, **Ignore**, **Mute**, and **Re-open** actions.
* Mention the Sazabi agent in a channel to investigate and get answers grounded in your data.
* Route issues to specific Slack channels through delivery rules.

Connecting Slack also makes its MCP tools available to the agent automatically — there is no separate MCP connector to set up.

## Prerequisites

* A Slack workspace where you can authorize app installation.
* Organization admin access in Sazabi.

## Set up in the dashboard

**Step 1**

### Open the Slack integration

In the dashboard, go to [**Settings > Integrations > Slack**](https://app.sazabi.com/settings/integrations/slack).

**Step 2**

### Install the Sazabi Slack app

Start the connection and authorize the Sazabi app in your Slack workspace.
Slack redirects you back to Sazabi when the install completes.

**Step 3**

### Route issues to a channel

On the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that
routes an event type (for example **Issue triggered**) to a Slack channel.
See [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

For asking the agent questions from Slack, see [Chat guide](https://docs.sazabi.com/guides/investigate/chat.md).

## Set up with the CLI

You can also start the Slack connection with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/integrations.md)).

Slack connects through an OAuth browser flow — the CLI has no `--credentials` for it. Run:

```bash theme={"system"}
sazabi integrations connect slack
```

The command opens Slack's authorization in your browser (sign in to the dashboard as the same user), then waits for you to install the Sazabi app in your workspace. `--json` changes only the output: the command still opens the browser and waits for the flow to finish, then prints the resulting connection as JSON:

```bash theme={"system"}
sazabi integrations connect slack --json
```

If the workspace is already connected to another Sazabi organization, the browser asks whether to move it before the install completes; the CLI keeps waiting for your decision. Then add a delivery rule so notifications reach a Slack channel — from the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, or with the CLI (`sazabi notifications delivery-rules create`; see [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md#delivery-rules)). Run `sazabi integrations list --provider slack` to confirm the connection.

## Chat with Sazabi

Once Slack is connected, mention the Sazabi agent in a channel or DM to start an investigation without leaving Slack — it answers grounded in your project's data. See [Chat outside the dashboard](https://docs.sazabi.com/guides/investigate/chat.md).

## Notifications

Use Slack as a delivery destination for issue and system events: on the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that routes an event type to a Slack channel. See [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Connected account

You can also connect your personal Slack account under [**Settings > Connected accounts**](https://app.sazabi.com/settings/connected-accounts) so the agent acts as you in Slack. When you have a personal connection Sazabi uses it first and falls back to this organization integration otherwise. See [Connected accounts](https://docs.sazabi.com/guides/administer/connected-accounts.md).

## Verify

With a delivery rule pointing at a Slack channel, trigger an issue event (for example, re-open the test issue Sazabi created with your first project from the project inbox) and confirm an issue card posts to that channel within a minute. The card should carry inline action buttons. If nothing posts, confirm the rule names both the event type and that channel, and that the Sazabi app is in the channel.

## Troubleshooting

**No card in the channel** — Confirm a delivery rule targets that specific channel and that the Sazabi app has been added to it.

**Connection shows needs attention** — The Slack app authorization may have been revoked. Reconnect from [**Settings > Integrations > Slack**](https://app.sazabi.com/settings/integrations/slack).

## Further reading

> [card] [Chat](https://docs.sazabi.com/guides/investigate/chat.md)
>
> Ask the Sazabi agent questions from Slack.

> [card] [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md)
>
> Route issues to Slack channels.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.