Slack Claude Connector

A connector is a connection to data, not a magic button. It tells Claude where to read. Whether the output is useful still depends on what you ask and how you check the result.

Slack is the team-chat half of the Email + Productivity pillar. If most of your work happens in channels, the Slack connector compresses the time spent reading them. Like Gmail, the underlying value is read-then-draft: Claude pulls the conversation, summarizes it, drafts your response, waits for you to send.

What is the Slack Claude connector?

The Slack Claude connector is a permission-controlled bridge to your Slack workspace. Once connected, Claude can read public channels you’re a member of, private channels you’ve granted access to, threads, DMs (if you grant DM scope), and search results. The default scope is read-only; sending messages or posting to channels requires explicit write scope you grant during setup. It uses Slack’s standard OAuth flow.

What can Slack do once Claude is connected?

• Read channels and threads. Pull recent messages, surface decisions made, classify by topic.
• Search across the workspace. “Find every mention of [project name] in the past 30 days.” Returns results from channels you have access to.
• Draft replies. Generate responses in your voice that wait for you to send.
• Read DMs (with scope). Triage direct messages, draft responses, surface unanswered conversations.
• Summarize threads. An 80-message thread becomes a 4-line summary plus the three decisions made.
• Workspace-wide context. Combined with other connectors (Linear, Notion, GitHub), Claude can answer “what’s the status of X” with cross-tool context.

How do I add the Slack connector?

1. In Claude, open the toolbox in the bottom-left, click Customize, then Connectors.
2. Click the +, then Browse connectors.
3. Find Slack in the directory. Click + on the card.
4. The Slack OAuth flow opens. Choose your workspace. Review the scopes (channels:read, search:read, chat:write_user is opt-in). If your workspace requires admin approval for new apps, you may see a request-approval flow first.
5. Test: “Summarize the last 10 messages in #general.” If they come back, Slack is live.

Some workspaces require admin approval before users can install third-party apps. If you see an approval-pending message instead of immediate access, ask your Slack admin to approve Claude in the workspace’s app management settings. For Slack Enterprise Grid orgs, the connector may need to be enabled at the org level.

Standout prompts for Slack

These are the prompts that exploit Slack’s specific capability rather than treating Claude like a generic chat tool. Copy, paste, modify the specifics.

• Channel Digest. “Summarize today’s #engineering channel. Flag any decisions made.” Replaces the morning scroll.
• Thread Summary. Pulls an 80-message thread, drafts a one-paragraph summary with the three biggest decisions or open questions.
• DM Triage. Reads unread DMs, classifies by urgency, drafts replies to the ones that need a response.
• Status from Slack Activity. Reads your own messages from the past week across channels. Drafts the weekly status update for your manager.
• Decision Audit. “What did we decide about [topic] in Slack over the past month?” Searches, surfaces every relevant message, drafts the consolidated decision summary.
• Question Catch-Up. Finds every @mention or DM you missed while heads-down or out, drafts a reply to each.
• Knowledge Search. “Find the link to the design doc Sarah shared three weeks ago.” Searches across your channels, returns the message.
• Cross-Channel Theme Surface. Reads multiple channels, surfaces the topic showing up in three or more places, drafts the briefing.
• Team Sentiment Pulse. Reads a channel over a defined window, surfaces tone shifts, flags topics that are heating up or cooling down.
• Slack-to-Ticket Loop. Combined with the Linear or Jira connector. Reads a Slack thread that includes an action item, drafts the ticket, files it with the right assignee.

What are the limits?

• Private channel and DM access is opt-in. By default Claude sees public channels you’re a member of. Private channels and DMs require additional scope.
• Send is opt-in. The connector defaults to read-only. Posting messages requires the chat:write_user scope during setup.
• Workspace admin approval may be needed. Many workspaces restrict third-party app installation. If you see a “requires approval” message, your Slack admin needs to approve Claude before you can use it.
• Message volume caps per query. A single prompt usually reads 50-200 messages. For longer audits, batch by channel and date range.

Is the Slack connector safe?

• For paid Claude plans, Slack data accessed via the connector is not used to train models and is not retained on Anthropic servers beyond the request.
• OAuth scopes are real and respected. Granting public-channel read does not give Claude access to private channels or DMs unless you add those scopes.
• Slack Enterprise Grid orgs can centrally manage Claude access via the org admin console. Coordinate with your IT team if you are in a regulated industry.
• Revoke from Settings → Connectors in Claude, then optionally also from your Slack workspace’s installed apps page.

When does a connector pay off vs. just chatting with Claude?

Connectors earn their setup time when the data updates faster than you can retype it, lives behind login, or runs into the thousands of items. For one-off questions about static information, plain Claude through the chat interface is faster than installing anything. The break-even is usually around the third time you would otherwise be copy-pasting context for the same kind of question. For the full list of connectors and which pillar each belongs to, see the Claude Connectors hub. If a term in this post is unfamiliar, the AI Glossary has plain-English definitions.

Frequently asked questions

Can Claude post messages on my behalf?

Only if you grant the chat:write_user scope during setup. Most readers should leave this off and use the draft-then-paste flow instead, where Claude drafts and you paste into Slack.

Does the connector work with Slack Enterprise Grid?

Yes, but admin approval at the org level may be required. If you’re in a Grid org, ask whoever administers it whether Claude is already enabled.

Can Claude see channels I’m not a member of?

No. The connector respects Slack’s existing channel-access model. If you can’t see it in Slack, Claude can’t either.

Will the connector consume my Slack message quota?

Slack does not bill per-message-read in standard plans. The connector uses the Conversations API which is included in your plan.

How is this different from Slack’s built-in AI features?

Slack’s native AI (Slack AI) operates inside Slack and bills separately. The Claude connector pulls Slack data into Claude, where you combine it with other connectors (Gmail, Linear, Notion). Different value proposition; many teams use both.

Can Claude summarize a channel I haven’t read in weeks?

Yes, up to Slack’s history limits (which depend on your Slack plan). Standard plans cap message history at 90 days; Pro and Business+ retain longer.

Does Claude see ephemeral messages or message edits?

Edits yes (the latest version). Ephemeral messages (only visible to one user) typically no, depending on Slack’s API behavior.

Sources

• Anthropic: Introducing Connectors · official launch and partner list
• Slack API documentation · what the Slack connector exposes
• Anthropic Trust Center · privacy and compliance posture
• Slack app management · admin approval reference
• Anthropic privacy notice · connector data handling

You might also like

• Claude Connectors Guide (2026) · the master hub
• Claude Connectors for Email + Productivity · the pillar this connector belongs to
• Gmail Claude Connector · the inbox-side sibling
• Google Drive Claude Connector · the #1 most-installed connector
• Best Claude Prompts for Meeting Notes · pairs naturally with Slack-thread workflows
• How to Use Claude AI · the beginner walkthrough
• Best Claude Prompts: 50 Examples · the broader prompt collection
• Best AI Prompts by Job and Use Case · 60+ prompt packs organized by role and artifact