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

# Slack

> Connect a client's Slack workspace so workflow alerts post to its channels, private channels and people.

## What This Integration Does

Connecting Slack lets a workflow's [Alert step](/user-guide/workflows#alert-step) post to the client's Slack workspace: a public channel, a private channel, or a direct message to a person. Messages can @mention people, user groups, `@here` and `@channel`.

Slack is connected per client. Each client signs in to its own workspace, and a client can connect more than one Slack account, for example two workspaces.

<Note>
  Slack alerts no longer use incoming webhook URLs. An Alert step that still has only a webhook URL stops sending until the client connects Slack and a channel is picked in the step.
</Note>

## Setup

<Steps>
  <Step title="Open the integration">
    Go to **Settings → Integrations**, find the **Notifications** section and open **Slack**.
  </Step>

  <Step title="Connect your account">
    Click **Connect Slack account**. Slack opens in a new window: choose the workspace and click **Allow**. The window closes and the account appears as `@your-name (Workspace)`. If your browser blocks the window, the same page opens in the current tab and brings you back afterwards.
  </Step>

  <Step title="Pick it in a workflow">
    In a workflow's Alert step, choose a client, then the Slack account, where to send and who sends it. See [Alert step](/user-guide/workflows#alert-step).
  </Step>
</Steps>

Your Slack workspace may require an admin to approve new apps. If so, Slack asks for approval instead of showing **Allow**.

## What RevyOps Can Do In Slack

| Permission | Used for |
| - | - |
| Post messages, also in public channels the bot hasn't joined | Sending alerts as the RevyOps bot |
| Open direct messages | Alerts to a person |
| Read the channel, people and user group lists | The pickers and @mentions in the Alert step |
| Post as you, and add the bot to your private channels | Alerts sent as your Slack account, and private-channel alerts sent as the bot |

RevyOps never reads message history.

## Sending As The Bot Or As Your Account

* **RevyOps bot**: messages come from the RevyOps app. In a private channel the bot has to be a member; RevyOps adds it for you when you pick the channel, using the connected account, which must be in that channel.
* **Slack account**: messages come from the person who connected Slack, so they can only go to channels that person is in.

## Disconnecting And Reconnecting

Click **Disconnect** next to an account to remove it. Alert steps that use it stop sending until another account is picked.

If the RevyOps app is removed from the Slack workspace, or the connected person loses access, the account shows as disconnected with the reason, alerts that use it fail with that reason, and the workflow can't be turned on for that client. Click **Reconnect** and allow access again: the same account comes back, and the Alert steps that used it work without picking it again.

## Limits

Slack allows about one message per second per channel. RevyOps paces each channel to that rate, and when Slack asks it to slow down, it waits and sends the message again, so a large workflow takes longer instead of losing messages.


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