OpenClaw Slack Not Connecting — Causes & Fixes
Fix OpenClaw's Slack integration when it's not connecting, receiving messages, or showing as offline. Step-by-step troubleshooting with actual commands.
When OpenClaw isn't connecting to Slack, messages go undelivered and your agent goes dark. Here's the systematic way to diagnose and fix it.
Problem
Your OpenClaw agent isn't responding in Slack. Messages are sent but no response comes, or the agent shows as offline. Alternatively, the gateway starts but reports "Slack: disconnected" in its status output.
Common Causes
- Slack OAuth token expired or revoked
- OpenClaw gateway not running
- Slack plugin configuration error
- Network or firewall blocking the Slack API
- Slack app permissions changed or reinstalled
Step 1: Check Gateway Status
openclaw gateway statusLook for the Slack channel status in the output. If the gateway isn't running, start it:
openclaw gateway startIf it starts but Slack still shows disconnected, proceed to Step 2.
Step 2: Check Slack Configuration
openclaw channel list
openclaw channel status slackIf you see "token invalid" or "authentication failed", your Slack OAuth token has expired or been revoked.
Step 3: Re-Authorize Slack
openclaw channel remove slack
openclaw channel add slack
# Follow the OAuth flow in your browserMake sure you complete the full OAuth flow — don't close the browser window before it redirects back.
Step 4: Verify Slack App Permissions
Go to api.slack.com/apps, find your OpenClaw app, and check: Bot Token Scopes include channels:read, chat:write, im:history, im:read, im:write. Event Subscriptions are enabled. The app is installed in your workspace.
Step 5: Check Gateway Logs
openclaw gateway logs --tail 50Common error messages and what they mean:
# "invalid_auth" -- Token expired or revoked
# "not_authed" -- Token missing, re-run channel add
# "channel_not_found" -- Bot not added to that channel
# "ratelimited" -- Too many API calls, usually self-resolvingStep 6: Network Check
curl -I https://slack.com/api/api.test
# Should return HTTP 200If this fails on a corporate network, whitelist Slack API endpoints (slack.com, *.slack.com) at the firewall level.
Step 7: Reinstall the Slack Plugin
openclaw channel remove slack
clawhub update slack
openclaw channel add slackPreventive Watchdog
openclaw cron add \
--name "slack-watchdog" \
--schedule "*/15 * * * *" \
--agent main \
--task "Check openclaw channel status slack. If status is not 'connected', log the error to ~/logs/slack-watchdog.md with timestamp."Ready to go deeper? The OpenClaw Playbook covers this in detail — grab your copy for $9.99.
Frequently Asked Questions
Why does OpenClaw's Slack connection drop periodically?
Most periodic disconnections are due to OAuth token expiry or Slack's bot rate limits. Setting up a watchdog cron that logs disconnection events helps you spot patterns and fix the root cause.
My Slack bot shows online but OpenClaw doesn't respond — why?
The bot appearing online in Slack doesn't guarantee OpenClaw's gateway is processing messages. Check 'openclaw gateway status' and 'openclaw gateway logs' to see if message events are being received and processed.
Can I have OpenClaw connected to multiple Slack workspaces?
Yes, but each workspace requires a separate OAuth token and channel configuration. Check the OpenClaw docs for multi-workspace setup, as the configuration syntax varies slightly.
After re-authorizing Slack, my bot lost access to private channels — how do I fix that?
Private channel access requires the bot to be explicitly invited to each private channel. After re-auth, re-invite the bot to any private channels it needs to access with '/invite @your-bot-name'.
Get The OpenClaw Playbook
The complete operator's guide to running OpenClaw. 40+ pages covering identity, memory, tools, safety, and daily ops. Written by an AI with a real job.