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

# Slack

> Let the Rippit agent read public Slack channels and deliver reports through the Rippit Slack app.

Slack is the most common connection, for two reasons: it is where the questions start, and it is where the answers need to land.

## What the agent gets

* **List public channels** and read their history and threads.
* **No access to private channels or DMs.**
* **Resolve users**, turning the user IDs in message payloads into names, emails, and titles.
* **Post messages as the Rippit Slack app**, in channels where the app is already a member or as DMs to explicitly selected users.

Typical uses: reading recent discussion in a known public channel, following a public thread where a bug was reported, or posting a weekly escalation summary into a channel on a schedule.

## Setup

Click **Connect** on Slack and authorize. There is nothing to create in Slack first.

Rippit reuses its existing Slack app, so authorizing covers both message delivery and read access in one approval. A Slack admin may need to approve the app if your workspace restricts installations.

## Identity and scope

The connection is organization-wide. Anyone in the Rippit organization, including Skills and scheduled Agent Apps, can use it to read public Slack channels. Private channels and DMs are excluded.

Messages are sent by the Rippit Slack app, not by the person who authorized the connection. The app can post in channels where it is already a member or send DMs to explicitly selected users.

## Tools

| Tool                        | Access | What it does                                                                                                                                                 |
| --------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `slack_list_channels`       | Read   | List public channels, with topic, purpose, and member counts. Set `writable_only=true` to narrow the list to channels where the Rippit Slack app is a member |
| `slack_get_channel_history` | Read   | Fetch recent messages from one channel, newest first                                                                                                         |
| `slack_get_thread_replies`  | Read   | Fetch a thread: the parent message plus its replies                                                                                                          |
| `slack_get_user_profile`    | Read   | Resolve a Slack user ID to name, email, title, and timezone                                                                                                  |
| `slack_list_users`          | Read   | List workspace members with names, emails, and titles                                                                                                        |
| `send_slack`                | Write  | Deliver a message or report to a channel where the Rippit Slack app is a member, or DM an explicitly selected user                                           |

`send_slack` is Rippit's own tool, not part of the Slack connection, and it is available automatically; it shows in the tool picker marked **automatic**. If you have used Slack MCP servers elsewhere and expect a `slack_send_message` tool, this is what replaces it.

Because delivery goes through the Rippit Slack app, a post to a channel where the app has not been invited fails. Invite the Rippit app to the channel and try again. When the agent is picking a channel destination it lists channels with `writable_only=true`, so it only offers channels the app can already post to. A DM destination uses the explicitly supplied Slack user email and still posts as the Rippit app.