Slack
Available from connector 2.114.
What Claude can do
- List channels
- Read a channel's history and a thread's replies
- List members and read a profile
Read-only: no message, reply or reaction is sent.
Everything the service returns is coded before it reaches Claude.
Before you start
Slack does not sign in through a login page but with the token of a Slack app that you (or your Slack administrator) create once:
- On api.slack.com/apps, create an app "From scratch" in your workspace.
- Under OAuth & Permissions → Bot Token Scopes, add only:
channels:read,channels:history,users:read,users.profile:read. - Install to Workspace, then copy the Bot User OAuth Token (it starts with
xoxb-). - Note the workspace ID (it starts with
T; visible in Slack's address in a browser). - In Slack, invite the app to the channels it should be able to read (
/invite @app-name).
Set up
- Hidden Tokens dashboard → Connectors.
- On the Slack row, click Enable.
- Paste the token and the workspace ID, then Save the token. It is stored encrypted in this computer's vault; it is shown neither to the AI nor on screen, and enters no file of the folder.
- Click Test. The status becomes "Ready".
Try it in Claude
Summarise this week's messages in #general.
Claude should use a slack__… tool and answer with codes. To get the real values back in a text, ask Hidden Tokens to decode it: they return to your computer, not to the chat.
Switch off the built-in connector
In Claude, Settings → Connectors and Extensions: switch off Slack. Otherwise the AI can go through it, in clear.
Limits
- Read-only. The app only sees the public channels it was invited to; not direct messages.
- "Test" checks that the connector starts, not that Slack accepts the token: a revoked token shows at the first call in Claude.
- Images and attachments are not passed to Claude.
- Not yet tried with a real Slack workspace or on Windows (9 Nov 2026).
A problem? See Troubleshooting.