Resources · Claude connector

Claude Slack connectorWhat Claude can do in your Slack account.

The Claude Slack connector exposes 11 tools. 8 of them read your workspace (search, channels, threads, canvases, profiles) and 3 write to it: one posts a message, two build or revise a canvas. Below: what Claude reaches, what it asks first, and who can switch it off.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes once Claude can read your Slack

A decision made three weeks ago in a busy channel is hard to dig out. With the connector on, you ask Claude in plain words and it runs the search itself, across public channels and the private ones you already belong to, then answers with what it found. It can also post the answer back or turn it into a canvas, one of Slack's formatted documents you can share.

Catch up after a week off. Claude pulls a channel's history with slack_read_channel and a long discussion with slack_read_thread, then sums up what was decided and who owns what.

Find the person, not just the message. slack_search_users and slack_read_user_profile return names, statuses and custom profile fields, handy when you need the right contact in another team.

Turn a conversation into a document. After a long thread, slack_create_canvas lays out a formatted recap, and slack_update_canvas adds to it as the project moves.

What the connector does not do matters just as much. Slack's own documentation describes scheduled messages, reactions, file uploads, lists and new channels, yet none of these appears among the 11 tools on the directory sheet, so Claude does not expose them here. Nothing runs by itself either: no tool wakes up when a message lands in a channel. For that kind of background flow, the Slack n8n integration and the Slack Make integration do a different job, on a trigger, without anyone in a chat.

Vocabulary

Five words before you connect

The vocabulary around this connector, in one minute.

Connector
The link you set up once between Claude and a Slack account you already use, so Claude can work in it while it answers you.
Tool
One named thing the connector lets Claude do, like reading a thread. Claude picks the tools it needs on its own while it replies.
Authorization
Slack's own sign-in screen, where you hand Claude the access it will use. You grant it once, for yourself, and you can take it back.
Approval
The confirmation Claude waits for in the conversation before it goes ahead with something that changes your workspace.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Slack.
Connect

Connect Slack to Claude in three steps

  1. 01

    Find Slack in the list

    Open Claude's settings, go to Customize then Connectors, and look for Slack. On a Team or Enterprise workspace, an Owner or Primary Owner enables it for the organization first, then each member connects their own account.

  2. 02

    Start the connection

    Click Connect on the Slack row and sign in to Slack in the window Slack opens itself. When the link works, the button reads Disconnect. If it ever breaks, disconnect and connect again.

  3. 03

    Check the authorization screen

    Read Slack's authorization screen before you accept it. That screen belongs to Slack, not to Claude, and it decides what the access covers. You can also withdraw the access later from the Slack side.

Tools

The 11 tools, split by what they do

Slack gives Claude 11 tools: 8 that read your account, 3 that change something in it.

Two groups: what Claude reads, and what it changes in your workspace. Tool names stay exactly as Claude shows them.

  • 8 read
  • 3 write

What Claude reads (8)

8 tools

Eight tools that look at messages, channels, canvases and people and leave them as they are.

slack_search_public_and_private

Searches messages and files across public channels and the private conversations you are part of, filtered by date, author or type. Claude gets back the matches with their details.

When it helps
you remember a pricing debate happened somewhere, but not whether it was in a private channel or a group chat.
Watch out
it only covers what your own Slack account can already open.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_search_users

Looks up people in the workspace by name, even a partial one, by email or by user ID, and brings back their details and current status.

When it helps
you know a colleague is called Priya something in finance and need her exact handle before asking Claude to draft a note for her.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_search_channels

Finds public and private channels by their name or their description, and returns each channel's metadata so Claude knows where a topic lives.

When it helps
a new hire asks where release notes get discussed, and nobody remembers if the channel is #releases or #ship-log.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_search_public

A narrower search that stays inside public channels. Same filters on date, author and content type, but private conversations stay out of the results.

When it helps
you want an answer you could safely paste into a company-wide thread, drawn only from what everyone can already see.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_read_channel

Pulls the full message history of one channel so Claude can read it in order rather than through scattered search hits.

When it helps
back from holiday, you ask for a summary of everything that happened in #customer-escalations since Monday.
Watch out
on a very active channel this is a lot of text for one conversation.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_read_thread

Fetches every reply of a single thread, from the first message to the last, so the context of a discussion comes through whole.

When it helps
a forty-reply debate about a vendor contract needs to become three bullet points for your manager.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_read_canvas

Exports an existing canvas as plain formatted text that Claude can read, quote and reason about in the chat.

When it helps
the onboarding checklist lives in a canvas and you want Claude to tell you which steps still apply to a contractor.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_read_user_profile

Returns someone's complete profile, including the custom fields your company added and their current status.

When it helps
before a call you ask Claude for a colleague's role, team and time zone as listed in Slack.
Watch out
it shows only what the profile holds; empty fields stay empty.

Sourcedocs.slack.dev · September 30, 2026 ↗

What Claude changes (3)

3 tools

Three tools that post or edit content in Slack. No source spells out their confirmation, so the general rule below applies.

slack_send_message

Approval: see the rule

Posts a message on your behalf into any kind of Slack conversation: a channel, a direct message or a group chat.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule below is what covers it.
When it helps
Claude drafted a status update from three threads and you want it posted in #team-weekly.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_create_canvas

Approval: see the rule

Builds a new canvas from scratch, with headings and formatting, ready to share with the people in a channel.

What Claude asks for
nothing documented for this tool on its own; the general approval rule applies.
When it helps
a retro thread ran long and you want a clean page of decisions and owners that the team can come back to.

Sourcedocs.slack.dev · September 30, 2026 ↗

slack_update_canvas

Approval: see the rule

Edits a canvas that already exists, so an existing page keeps growing instead of a new one appearing each week.

What Claude asks for
no source gives this tool its own confirmation step; see the general rule below.
When it helps
the project tracker canvas needs this week's blockers added after the stand-up.
Watch out
anyone with access to the canvas sees the edits.

Sourcedocs.slack.dev · September 30, 2026 ↗

Approvals

What Claude checks with you first

By default, Claude stops and asks before each action it takes on an account for someone. The prompt shows up in the conversation at the moment it matters.

On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keeping search on and posting off. That setting binds everyone, and nobody lifts it from a personal account. Claude also works with the rights of the person who connected and nothing beyond: a private channel you are not in stays out of its reach.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, which is a real hole in the catalog.

What Anthropic does publish is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. Anthropic's own Slack page says something narrower, and the limits section below sets both texts side by side. For the live state on your account, the connector's sheet in the official directory is the place to look.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you, so nothing fires when a message arrives, a thread heats up or someone mentions you.

The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge in the directory is not a security audit either, and Anthropic states on every sheet that it neither picks the tools a publisher exposes nor guarantees they behave as announced. Here the publisher is Slack itself. For a connector whose own official sources contradict each other on what it can send, the Claude gmail connector page walks through that case.

Two official sources disagree

Which Claude plans can use the Slack connector?

What this page followsThe Slack page is the only Anthropic text aimed at this connector, so it is the more specific one, but it carries no date and also covers the older Claude in Slack app. Neither text settles it for your account: check the directory sheet while signed in.

Need help

Need help connecting Slack to Claude?

A person reads every message.

FAQ

Questions about the Claude Slack connector

01What can Claude do with the Slack connector?
Claude can search and read your Slack workspace, then act on it from the conversation. Its 11 listed tools cover searching messages and files, finding people and channels, reading full channels and threads, reading canvases and profiles, posting a message, and creating or updating a canvas. Anthropic's Slack page puts the focus on search: Claude looks through channels, direct messages and files to answer your question, and it stays within what your own Slack account can open.
02Can Claude post messages or edit things in Slack?
Yes, three of the tools write. One posts a message on your behalf into a channel, a direct message or a group chat, one creates a new canvas and one edits an existing canvas. Nothing else is exposed: Slack's own documentation mentions scheduled messages, reactions, uploads and lists, but none of these has a tool on the directory sheet. On Team and Enterprise workspaces, an owner can keep reading on and switch writing off for everyone in the organization.
03Does Claude ask before it posts in Slack?
By default, yes: Claude asks for confirmation before each action it takes on an account on someone's behalf, and the prompt appears in the conversation. No source describes a specific confirmation for posting a message or editing a canvas, so that default rule is what covers them. On Team and Enterprise workspaces, owners decide whether members may let some actions run without being asked every time, and that choice applies to the whole organization.
04Which plans is the Slack connector available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. Anthropic's general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner enabling them first on Team and Enterprise. Anthropic's Slack page gives a narrower answer, quoted on this page next to the general rule. The directory sheet, opened while signed in, is the only place showing the current state for you.
05Can Claude read every channel in our workspace?
No, Claude works with your rights and nothing more. It inherits the permissions of the person who connected, so private channels and direct messages you are not part of stay out of reach. Two people asking the same question can get different answers because their access differs. Beyond that, an owner on a Team or Enterprise workspace can narrow what the connector may do for everyone. On the other side, the workspace admins can refuse or remove the Claude app entirely.
06Why can't I switch on the Slack connector?
Most often because the Claude in Slack app is not installed in your workspace yet. Anthropic's Slack page asks for that app first, and Slack says its workspace admins approve and manage such integrations. On a Team or Enterprise workspace, an Owner then enables the connector once for the organization, after which each member connects their own account. If your Slack app restricts IP ranges, requests from Claude can also be refused.
07Should I use Claude or an automation tool with Slack?
They do different jobs, so it depends on what you need. Claude works inside a conversation: you ask, it searches, summarizes or posts, and it stops when you stop. Nothing fires when a message arrives in a channel. When you need Slack to react on its own, say forwarding every new support message somewhere, that belongs to an automation tool running on a trigger. For answers and quick write-ups on demand, the connector fits.