Give your AI agent safe access to Slack
Let your agent work across your Slack workspace — reading channels, searching conversations, posting updates, replying in threads, and keeping your team in the loop.
You decide which channels it can touch and what it can do in each one. Nothing gets posted without matching the rules you've set.
Step 1
Connect your Slack workspace
Open the AgentBlocks dashboard, click “Connect Slack,” and sign in to your workspace. That's the setup. Your agent now has access to Slack — but only within the rules you're about to set. You can disconnect at any time from your Slack admin settings.
Superpowers
Jane Smith
jane@example.com
Slack
Send messages and read channels in Slack
Slack not yet connected
Connect your Slack workspace to give your agent access to channels, messages, and more.
Step 2
Set your Slack rules
Let your agent read freely across the channels you're happy for it to see, and step in when it matters. Approve posts before they go live. Block it from certain channels entirely. Set rules per channel so your agent can post automatically in #ai-updates but always check with you before anything lands in #clients or #leadership.
You also control the smaller stuff — whether it can react with emoji, reply in threads, or upload files — each one with its own rules, each one per channel.
Reading
What your agent can see in Slack. These actions don't send anything or change anything.
List channels
See all channels and their names in your workspace.
List workspace members
See who is in your Slack workspace.
Read user profiles
View details about specific users, like their name and status.
Search messages
Search through your workspace’s message history. Results are automatically filtered to channels your agent can read.
Read files
Access files that have been shared in channels.
Read messages
Set which channels this agent can read messages from.
Sending & Posting
Actions that send content or interact with messages on your behalf.
Post messages
Set which channels this agent can post messages to.
Reply to threads
Set which channels this agent can reply in.
Add reactions
Set which channels this agent can add reactions in.
Upload files
Set which channels this agent can upload files to.
Step 3
Connect your agent
Open your AI tool — Claude, Manus, whatever you use — and add AgentBlocks as a connector. Two clicks. Your agent instantly knows it has Slack access and exactly which channels it can work in.
Add custom connector
BETAConnect Claude to your data and tools. Learn more about connectors or get started with pre-built ones.
AgentBlocks
https://mcp.agentblocks.ai/v1
Advanced settings
Only use connectors from developers you trust. Anthropic does not control which tools developers make available and cannot verify that they will work as intended or that they won't change.
Step 4
It reads and gathers context on its own
Ask your agent to catch you up on what's happening. It reads channels, follows threads, searches for what's relevant, and pulls everything together. All of this happens automatically based on your rules — no interruptions while it's listening in.
Step 5
Posting and replying need your approval
When your agent wants to post something, it pauses. You see the exact channel, the full message, and who's going to see it — before it's actually posted. One tap to approve, and it lands in Slack instantly. If you want to change the wording first, you can edit before approving.
AgentBlocks
WhatsApp approval
Your agent wants to post this message to your Slack workspace.
Channel: #engineering
Daily Standup Summary — Wed 18 June
Completed yesterday: Shipped payment retry logic (PR #482 merged), resolved 3 Sentry alerts in auth service.
Today: Load-test payment flow, start API rate-limiting design doc.
Blockers: None — staging deploy is green.
15:22
✓ Posted to #engineering
15:22
And it appears in the channel instantly
The message shows up in the target channel exactly as you approved it. Your team sees it, threads form around it, and your agent keeps working in the background — already drafting the next thing.
PR #482 is merged. Staging is green ✅
Daily Standup Summary — Wed 18 June
Completed yesterday: Shipped payment retry logic (PR #482 merged), resolved 3 Sentry alerts in auth service.
Today: Load-test payment flow, start API rate-limiting design doc.
Blockers: None — staging deploy is green.
Step 6
Then let it run
Once you're comfortable with your rules, your agent works across your workspace on its own — reading channels, following threads, searching conversations, and drafting messages throughout the day. It only surfaces when there's something to post in a channel that needs your approval. You tap approve from your phone and it keeps going.
7
This session
5
Auto-approved
2
Waiting for you
14:00
Listed channels
24 channels accessible
14:01
Read messages in #engineering
Last 50 messages — deployment, PRs, Sentry alerts
14:02
Read messages in #product
Last 50 messages — feature launches, customer feedback
14:03
Read thread: deployment pipeline discussion
12 replies — CI/CD status updates parsed
14:05
Searched messages: "payment retry"
8 matches across #engineering, #incidents, #product
14:12
Post message to #engineering
Daily Standup Summary — Wed 18 June
14:12
Post message to #product
Weekly feature progress update
Explore other superpowers
Every integration works the same way — scoped access, approval controls, full audit trail.
Give your agent safe
Slack access today.
Connect your account, set your rules, and your agent takes it from there.
🦞 Works great with OpenClaw and Claude Cowork