Slackbot

Slackbot

Slackbot

Slack is a team communication platform with channels, direct messages, file sharing, and workflow automation. This integration uses managed OAuth through ClawLink to provide comprehensive Slack workspace automation -- from messaging and channel management to file handling, reactions, reminders, and canvases.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│   Slack API      │
│   (User Chat)   │     │   (OAuth)    │     │                  │
└─────────────────┘     └──────────────┘     └──────────────────┘

Install

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Quick Start

Send a message to a channel:

clawlink_execute_tool --integration slackbot --tool slackbot_send_message --args '{"channel": "C01234567", "markdown_text": "Deployment complete. All systems operational."}'

Search for messages in the workspace:

clawlink_execute_tool --integration slackbot --tool slackbot_search_messages --args '{"query": "quarterly report"}'

List all channels in the workspace:

clawlink_execute_tool --integration slackbot --tool slackbot_list_all_channels

Authentication

Slack uses OAuth 2.0 managed by ClawLink. No API keys are needed. Authorize your Slack workspace through the ClawLink dashboard. The connection is stored securely and refreshed automatically.

Connect at: https://claw-link.dev/dashboard?add=slackbot

Connection Management

List connections:

clawlink_list_integrations

Verify connection:

clawlink_execute_tool --integration slackbot --tool slackbot_fetch_team_info

Reconnect: If a connection expires, visit the dashboard URL above and reconnect Slack.

Security & Permissions

• Read operations (listing channels, messages, users, files, searching) are safe and require no confirmation.
• Write operations (sending messages, creating channels, scheduling, managing reactions) modify data and require confirmation.
• Destructive operations (deleting messages, files, canvases, scheduled messages) are high-impact and irreversible.

Tool Reference

Messaging (Chat)

Channel (Conversation) Management

User Operations

File Operations

Remote File Operations

Reaction Operations

Pin Operations

Reminder Operations

Call Operations

Canvas Operations

User Group Operations

Search Operations

Team & Emoji Operations

DND (Do Not Disturb) Operations

Code Examples

Send a message to a channel:

{
  "tool": "slackbot_send_message",
  "args": {
    "channel": "C01234567",
    "markdown_text": "Build completed successfully. See details at https://ci.example.com/123"
  }
}

Schedule a message for later:

{
  "tool": "slackbot_schedule_message",
  "args": {
    "channel": "C01234567",
    "post_at": 1750000000,
    "text": "Standup starts in 10 minutes!"
  }
}

Search messages with filters:

{
  "tool": "slackbot_search_messages",
  "args": {
    "query": "from:@john in:#engineering after:2026-05-01"
  }
}

Create a channel and invite users:

{
  "tool": "slackbot_create_channel",
  "args": {
    "name": "project-phoenix",
    "is_private": false
  }
}

Add a reaction to a message:

{
  "tool": "slackbot_add_reaction_to_an_item",
  "args": {
    "channel": "C01234567",
    "timestamp": "1234567890.123456",
    "name": "thumbsup"
  }
}

Discovery Workflow

1. Call clawlink_list_integrations to confirm slackbot is connected.
2. Call clawlink_list_tools --integration slackbot to see the live catalog.
3. Use slackbot_list_all_channels to discover channels (returns channel IDs needed for other tools).
4. Use slackbot_find_users to locate specific users.

Execution Workflow

Read Flow:
  list_all_channels → retrieve_conversation_information → fetch_conversation_history
  find_channels → get channel ID → fetch_conversation_history → fetch_message_thread

Write Flow:
  find_channels → get channel ID → send_message (confirm)
  find_users → open_dm → send_message (confirm)

Search Flow:
  search_messages / search_all → retrieve results → act on specific messages

Notes

• Always use resolved channel IDs (not display names) for operations. Names may be non-unique.
• fetch_conversation_history only returns main channel timeline messages. For threaded replies, use fetch_message_thread_from_a_conversation with the parent message's thread_ts.
• Sending messages is not idempotent -- duplicate calls create duplicate messages.
• Rate limiting applies at approximately 1 request per second for message posting. Honor Retry-After headers on 429 responses.
• Threaded replies require the parent message's ts value, not the thread's ID.
• When opening a DM, use open_dm first to get the DM channel ID, then use that ID with send_message.

Error Handling

Troubleshooting

Tools Not Visible

Run clawlink_list_tools --integration slackbot to verify the integration is active. If empty, reconnect at https://claw-link.dev/dashboard?add=slackbot.

Channel Not Found

Use slackbot_find_channels with exact_match=false to locate channels. Channel names are converted to lowercase. Private channels require the bot to be a member.

Message Not Sent

Verify the bot is a member of the target channel. Use find_channels to confirm the channel ID is correct. Check that markdown_text or blocks content is provided.

Thread Replies Not Found

Use fetch_message_thread_from_a_conversation with the parent message's thread_ts, not the channel's ts. The parent message's thread_ts is found in fetch_conversation_history results.

Resources

• Slack API Docs: https://api.slack.com/docs
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=slackbot
• ClawLink Docs: https://docs.claw-link.dev/openclaw

---

Powered by ClawLink -- an integration hub for OpenClaw

ClawLink Logo