OpenClaw Slack Integration: Connect Your Team's Social Media

Why Connect OpenClaw to Slack?

Your team already lives in Slack. That's where decisions get made, links get shared, and half the workday happens. So when you want an AI agent handling social media, it makes sense to put it where everyone already is.

OpenClaw supports Slack as a native channel. Not through some janky webhook — actual real-time messaging with threading, DMs, channel mentions, and streaming responses (the bot types in real-time, just like a human teammate). Your team can message the bot, get content drafts, approve posts, and trigger publishing without leaving Slack.

The setup takes about 15 minutes. Most of that time is spent in Slack's API dashboard creating the app and copying tokens. The OpenClaw side is three config lines.

This guide walks through the full process — from creating the Slack App to running team social media workflows. If you're brand new to OpenClaw, start with our beginner's tutorial first. This article assumes you already have OpenClaw running somewhere (locally or on a VPS).

What You Need Before Starting

Quick checklist:

• OpenClaw installed and running — local machine or VPS, either works
• A Slack workspace where you have admin permissions (or can request app installation)
• A Slack account on a paid or free plan — both work
• 15 minutes of uninterrupted time (the token-copying part is annoying if you get interrupted)

If you're running OpenClaw on a VPS behind a firewall, you'll want Socket Mode (covered below). It doesn't need a public URL. Events API does.

Step 1: Create a Slack App

Go to api.slack.com/apps and click Create New App.

Pick From scratch (not "from an app manifest" — we'll configure manually so you understand what each setting does).

Give it a name. Something like "OpenClaw" or "Social Media Bot" — your team will see this name in Slack, so make it recognizable. Select your workspace.

Enable Socket Mode

This is the step most tutorials bury halfway through, but you should do it first.

Go to Socket Mode in the left sidebar. Toggle it on.

Slack will ask you to generate an App-Level Token. Name it something like openclaw-socket and add the connections:write scope. Click Generate.

Copy this token somewhere safe. It starts with xapp-. You'll need it in a minute.

Why Socket Mode? Because it creates a WebSocket connection from your OpenClaw instance to Slack's servers. No inbound ports needed. No public URL. No SSL certificate. It just works — even behind corporate firewalls and NATs.

The alternative (Events API) requires a publicly accessible HTTPS endpoint. If you're running OpenClaw on a VPS with a domain and SSL already configured, Events API is fine. For everyone else, Socket Mode is the answer.

Set Up OAuth Scopes

Go to OAuth & Permissions in the sidebar. Scroll to Bot Token Scopes and add these:

Required scopes:

• channels:history — read messages in public channels
• chat:write — send messages
• im:history — read DM messages
• app_mentions:read — respond when someone @mentions the bot

Recommended scopes (for full functionality):

• channels:read — list channels
• groups:history — read messages in private channels
• groups:read — list private channels
• im:read — list DMs
• files:read — access shared files
• files:write — upload files (for generated images)
• reactions:write — add emoji reactions (useful for acknowledgment)
• users:read — get user info for personalized responses

Missing scopes are the #1 cause of "openclaw slack not working" issues. If OpenClaw connects but can't read messages or respond, you're almost certainly missing a scope. The error logs will say missing_scope — just add whatever scope it asks for and reinstall the app.

Subscribe to Events

Go to Event Subscriptions. Toggle it on.

If you're using Socket Mode (recommended), you don't need a Request URL. Skip that field.

Under Subscribe to bot events, add:

• message.channels — messages in public channels
• message.groups — messages in private channels
• message.im — direct messages
• app_mention — @mentions

These tell Slack which events to forward to your OpenClaw instance.

Install the App

Go to Install App in the sidebar. Click Install to Workspace. Authorize it.

You'll get a Bot User OAuth Token (starts with xoxb-). Copy this too.

Now go to Basic Information and scroll to App Credentials. Copy the Signing Secret.

You should now have three values:

1. App Token (xapp-...) — from Socket Mode setup
2. Bot Token (xoxb-...) — from Install App
3. Signing Secret — from Basic Information

Step 2: Configure OpenClaw

Three commands. That's it.

openclaw config set channels.slack.botToken "xoxb-your-bot-token"
openclaw config set channels.slack.appToken "xapp-your-app-token"
openclaw config set channels.slack.signingSecret "your-signing-secret"

Enable the Slack channel:

openclaw config set channels.slack.enabled true

Restart the gateway:

openclaw gateway restart

Check the connection:

openclaw channels status

If you see slack: connected — you're done. Open Slack, send a DM to your bot, and it should respond.

You can also configure these settings visually in the OpenClaw Dashboard's Configuration tab if you prefer clicking over typing.

Using Environment Variables Instead

If you'd rather not store tokens in OpenClaw's config file (smart move — see our OpenClaw security guide for why), use environment variables:

export OPENCLAW_SLACK_BOT_TOKEN="xoxb-your-bot-token"
export OPENCLAW_SLACK_APP_TOKEN="xapp-your-app-token"
export OPENCLAW_SLACK_SIGNING_SECRET="your-signing-secret"

OpenClaw reads these at startup. Add them to your .bashrc, .zshrc, or — better yet — a secret manager like Doppler or AWS Secrets Manager.

Step 3: Invite the Bot to Channels

Your bot exists in the workspace but it can only see channels it's been invited to. In Slack:

/invite @OpenClaw

Or just @mention it in any channel. Slack will ask if you want to invite the bot — say yes.

For team social media workflows, I'd recommend creating dedicated channels:

• #social-drafts — where the bot shares content drafts for review
• #social-approved — approved content waiting to publish
• #social-published — notifications when posts go live

More on this workflow in the team section below.

Team Social Media Workflows in Slack

Here's where the Slack integration actually shines. Individual use is fine — you can DM the bot just like you would in any other chat interface. But the team angle is what makes Slack worth the setup effort.

The Draft-Review-Publish Workflow

Set up three channels and configure your agent:

In #social-drafts: Team members ask the bot to create content. "@OpenClaw write a LinkedIn post about our new feature launch." The bot drafts it right in the channel where everyone can see it.

Review in-thread: Team members reply in the thread with feedback. "Make the hook stronger" or "Add the pricing." The bot revises in the same thread — full conversation context preserved.

Approval: Someone reacts with a ✅ emoji (or whatever you configure). The bot moves the approved content to #social-approved or publishes directly, depending on your setup.

In #social-published: The bot posts confirmation with links to each platform where it published. Everyone sees what went live without having to check 13 different platforms.

If you've set up OpenClaw for social media with skills like Social Poster and Content Forge, this workflow is what it was designed for. The Slack integration is the collaboration layer on top.

Scheduled Content Reviews

Use OpenClaw's cron jobs to post a weekly content summary in #social-published:

openclaw cron add --name "weekly-recap" \
--schedule "0 9 * * MON" \
--channel slack:#social-published \
--prompt "Summarize everything we posted last week. Include platform, engagement numbers if available, and top performers."

Monday morning, the bot drops a recap in your channel. No dashboards to check, no analytics tools to log into.

Who Can Talk to the Bot?

By default, anyone in your Slack workspace can message the bot. If you want to restrict access:

openclaw config set channels.slack.allowedUsers '["U01ABC123", "U02DEF456"]'

Use Slack user IDs (not display names — those aren't unique). Find IDs by clicking a user's profile in Slack → three dots → Copy member ID.

Or restrict by channel — only respond in specific channels:

openclaw config set channels.slack.allowedChannels '["C01ABC123", "C02DEF456"]'

Socket Mode vs Events API

Quick comparison for the technically curious.

| Socket Mode | Events API

**How it works** | WebSocket connection outbound | HTTP POST to your endpoint

**Public URL needed?** | No | Yes (HTTPS with valid cert)

**Firewall-friendly?** | Yes — outbound only | No — needs inbound port

**Setup complexity** | Lower | Higher

**Latency** | ~50ms | ~100-200ms

**Scale limit** | Single connection | Multiple endpoints

**Best for** | Most users | High-traffic production

Socket Mode is the right default. Switch to Events API only if you're running multiple OpenClaw instances behind a load balancer and need to distribute incoming events across them.

To switch to Events API, you'd set a Request URL in Event Subscriptions (Slack's dashboard) pointing to your OpenClaw gateway's webhook endpoint: https://your-domain.com/api/slack/events. Make sure your gateway is publicly accessible with HTTPS. See our VPS hosting guide for the Nginx/Caddy SSL setup.

Troubleshooting Common Issues

"missing_scope" Error

The most common problem. Your bot tries to do something it doesn't have permission for.

Check your OpenClaw logs for the specific scope name:

openclaw logs --filter "missing_scope" --last 50

The log will tell you exactly which scope is missing. Go to OAuth & Permissions in your Slack app settings, add the scope, then reinstall the app to your workspace. Adding scopes without reinstalling does nothing — Slack only applies new permissions on reinstall.

Bot Doesn't Respond in Channels

Three things to check:

1. Is the bot invited to that channel? /invite @OpenClaw
2. Is app_mention event subscribed? Check Event Subscriptions in the Slack App dashboard.
3. Did you @mention the bot? In channels, the bot only responds to @mentions by default. In DMs, it responds to everything.

If it works in DMs but not channels, it's almost always #2.

"Connection Closed" or Frequent Disconnects

Socket Mode connections can drop if your server's internet is unstable or if there's a long period of inactivity. OpenClaw has built-in reconnection logic, but if you're seeing frequent drops:

openclaw config set channels.slack.socketMode.pingInterval 30

This sends a keepalive ping every 30 seconds (default is 60). Helps on flaky connections.

If you're behind a corporate proxy that kills idle WebSocket connections, talk to your IT team about allowlisting Slack's WebSocket endpoints.

"Plugin Not Available" Error

This means the Slack channel plugin isn't installed or enabled in your OpenClaw instance. Fix it:

openclaw plugin install slack
openclaw config set channels.slack.enabled true
openclaw gateway restart

On some older OpenClaw versions, the Slack plugin ships separately. Current versions (March 2026+) include it by default.

Messages Arrive But Bot Doesn't Respond

Check if your agent is actually running:

openclaw agents status

If the agent is idle or stopped, it won't process incoming Slack messages. Restart it:

openclaw agents start <agent-name>

Also verify your OpenClaw skills are loaded. An agent without skills can receive messages but can't do much with them.

Security Considerations

A few things worth noting from a security best practices perspective:

• Never share your Bot Token or App Token publicly. Treat them like passwords. If you accidentally commit them to Git, rotate immediately in the Slack API dashboard.
• Use environment variables for tokens instead of config files (covered above).
• Restrict channel access if your workspace has sensitive channels the bot shouldn't read.
• Review the bot's scopes periodically. Remove any you're not using — principle of least privilege.
• Slack's free plan stores 90 days of message history. If your bot handles sensitive content, keep this retention policy in mind.

Or Skip All of This

That was a lot of steps. Creating the Slack App, copying tokens, configuring scopes, subscribing to events, troubleshooting missing_scope errors.

And that's just getting connected. You still need to set up OpenClaw skills, configure your agent for social media, and maintain the whole setup.

If your goal is team social media management and you don't want to play sysadmin, PostClaw does all of this out of the box. Same OpenClaw AI engine underneath. Same content quality. But you just open the chat and start talking — no Slack Apps to create, no tokens to manage, no scopes to debug.

$29/month. All 13 platforms preconfigured. Post to 13 platforms from a single conversation.

The Slack integration is great for teams that want OpenClaw embedded in their existing workflow. But if you're a solopreneur or small team that just wants the content creation and publishing handled, the self-hosted Slack setup might be more complexity than you need.

Getting Started

Already have OpenClaw? Here's the quick path:

1. Go to api.slack.com/apps → Create New App → From scratch
2. Enable Socket Mode → generate App Token (xapp-)
3. Add OAuth scopes → install to workspace → copy Bot Token (xoxb-) and Signing Secret
4. Subscribe to bot events: message.channels, message.im, app_mention
5. Configure OpenClaw: three openclaw config set commands + gateway restart
6. Invite the bot to your channels and start messaging

If you run into issues, the troubleshooting section above covers the five most common problems. And for the full picture on What Is OpenClaw and what else it can do beyond Slack, our complete guide covers the ecosystem.