slack-integration
Use when you need to control Slack from Clawdbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Permissions
Risk Assessment
This skill requests 1 of 4 possible permissions. Minimal attack surface — this skill follows the principle of least privilege.
SKILL.md
Overview
Use slack to react, manage pins, send/edit/delete messages, and fetch member info. The tool uses the bot token configured for Clawdbot.
Inputs to collect
channelIdandmessageId(Slack message timestamp, e.g.1712023032.1234).- For reactions, an
emoji(Unicode or:name:). - For message sends, a
totarget (channel:<id>oruser:<id>) andcontent.
Message context lines include slack message id and channel fields you can reuse directly.
Actions
Action groups
| Action group | Default | Notes |
|---|---|---|
| reactions | enabled | React + list reactions |
| messages | enabled | Read/send/edit/delete |
| pins | enabled | Pin/unpin/list |
| memberInfo | enabled | Member info |
| emojiList | enabled | Custom emoji list |
React to a message
{
"action": "react",
"channelId": "C123",
"messageId": "1712023032.1234",
"emoji": "✅"
}
List reactions
{
"action": "reactions",
"channelId": "C123",
"messageId": "1712023032.1234"
}
Send a message
{
"action": "sendMessage",
"to": "channel:C123",
"content": "Hello from Clawdbot"
}
Edit a message
{
"action": "editMessage",
"channelId": "C123",
"messageId": "1712023032.1234",
"content": "Updated text"
}
Delete a message
{
"action": "deleteMessage",
"channelId": "C123",
"messageId": "1712023032.1234"
}
Read recent messages
{
"action": "readMessages",
"channelId": "C123",
"limit": 20
}
Pin a message
{
"action": "pinMessage",
"channelId": "C123",
"messageId": "1712023032.1234"
}
Unpin a message
{
"action": "unpinMessage",
"channelId": "C123",
"messageId": "1712023032.1234"
}
List pinned items
{
"action": "listPins",
"channelId": "C123"
}
Member info
{
"action": "memberInfo",
"userId": "U123"
}
Emoji list
{
"action": "emojiList"
}
Ideas to try
- React with ✅ to mark completed tasks.
- Pin key decisions or weekly status updates.
Why You Need slack-integration
Slack is where your team communicates, but it sits outside your coding workflow. Switching to Slack to post updates, check messages, or share results breaks your flow. And if you are running autonomous agents, they have no way to notify your team of progress or ask for approvals.
Slack Integration connects your OpenClaw agent directly to Slack. Send messages to channels, read recent conversations, respond to threads, and post formatted updates — all from within your agent workflow. Your agent can notify the team when a deployment finishes, post test results, or ask for a code review.
Whether you are automating team notifications or building an agent that collaborates with your team in Slack, this skill bridges the gap between your AI workflow and your team's communication hub.
Common Use Cases
- Post automated deployment notifications to your team's Slack channel
- Send formatted test results or build status updates after CI runs
- Read recent messages in a channel to gather context before starting a task
- Notify a specific team member when their code review is ready
- Build an agent that responds to questions in a Slack channel with research results
Frequently Asked Questions
Does it need a Slack bot token?
Yes. You need a Slack bot token with appropriate scopes (chat:write, channels:read, etc.). The skill uses the Slack CLI tool that must be configured with your workspace.
Can it read and respond in threads?
Yes. It can read thread replies, post in threads, and manage threaded conversations. This is useful for keeping updates organized in busy channels.
Does it support direct messages?
Yes, as long as the bot token has the im:write scope. It can send direct messages to individual users in your Slack workspace.