# Slack Integration | Rippit

> Connect Slack to Rippit. Bring in threads from the channels you pick, and post findings where your team works.

Canonical: https://www.rippit.com/integrations/slack

Data integrationMCP connector

# Slack

Bring in every one of your Slack threads so Rippit can read all of them, and connect in real time to search channels and post findings in real time.

[Connect Slack](https://app.rippit.com/signup)[View Slack docs](https://www.rippit.com/integrations/docs/bulk-ingest#d-slack-i)

## Connecting Slack to Rippit

Data integration

### Rippit reads every one of your Slack threads

Brings your Slack threads into Rippit so all of it can be read, not a sample. A Rippit admin connects it once. It joins the channels you pick and only replies privately to whoever invites it. Nothing else changes in Slack.

[What you can do](#can)

MCP connector

### Agents look things up and act in Slack

Lets Rippit’s agents look things up in Slack the moment they need to, in chat, or in scheduled Agent Apps when it’s shared. A Full Admin adds it once under Connections. The connection is shared with your whole organization.

[MCP tools](#acts)

## What you can do with Slack data in Rippit

[How the Slack data integration works](https://www.rippit.com/integrations/docs/bulk-ingest#d-slack-i)

1.  1
    
    ### Label every record with AI columns
    
    A model reads each row and applies the judgment you describe, like its topic, its sentiment, or whether it reports a bug. It runs once per record as records arrive.
    
2.  2
    
    ### Ask questions across every conversation
    
    Ask in chat about what changed or what’s missing, and Rippit reads across the entire set, not a sample.
    
3.  3
    
    ### Query it as tables
    
    Every conversation is stored as a table you can query and build reports from, so results come back fast and your helpdesk isn’t under analysis load.
    
4.  4
    
    ### Join it with your other data
    
    Use lookups and rollups to bring in accounts, orders or product usage from other tables, and roll findings up by account, topic or week.
    
5.  5
    
    ### Run it on a schedule
    
    Turn the analysis into a pipeline that runs hourly, daily, weekly or monthly, and sends the result to Slack or email.
    

## What you can do with the Slack MCP connector

**7**actions

**6**read

**1**write

[How the Slack MCP connector works](https://www.rippit.com/integrations/docs/real-time#d-slack-c)

### Read & Search

On by default

-   **List Channels**List public channels with topic, purpose, member counts
-   **Lookup Channel**Find one public channel by ID or name
-   **Get Channel History**Fetch recent messages from one channel
-   **Get Thread Replies**Fetch a thread's parent message and replies
-   **Get User Profile**Resolve a user ID to name, email, title, timezone
-   **List Users**List workspace members with names, emails, titles

### Create & Update

Always on

-   **Send Slack**Post a message to a channel or DM a user

Posting is always on. Admins can turn off any read action.

## Your data and creativity is your edge. Put agents on it to maximize it.

Connect your data. Launch agents.

[Start free →](https://app.rippit.com/signup)[Book a demo](https://www.rippit.com/request-demo)

## Getting started from an AI agent

There are two ways to connect. Either works.

- MCP server: `https://mcp.rippit.com/mcp` (Streamable HTTP, OAuth). The person signs in or signs up in the browser that opens. No client ID, secret or API key is needed.
- CLI: install with `curl -fsSL https://rippit.sh | sh`, then get an account one of two ways:
  - `rippit login`: the person signs in or signs up in a browser.
  - `rippit start`: creates a temporary account with no email or browser, for a person with no Rippit account. `rippit claim --wait` lets them keep it; an unclaimed account is deleted after 14 days.

Then bring in data: connect a provider such as Zendesk, Intercom, Gong or Salesforce, or upload a CSV.

Full steps: https://www.rippit.com/setup.md