How to connect Slack to OpenClaw

The ClawHub skill teaches OpenClaw about Slack, but the calls run through the ClawLink plugin and your connected account. Make sure Slack is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Reconnect Slack from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Slack tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Slack call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

The error name is Slack's and it means the installed authorization does not carry the permission that one call needs. On a self-built app the documented fix is to add the scope in your app configuration and reinstall to the workspace, because Slack does not grant new scopes to an existing install — that reinstall step is what most search results are describing. On a hosted connection you do not own the app configuration, so the equivalent action is to reconnect from the ClawLink dashboard, which runs the install again and picks up the full permission set. Before doing that, rule out the cheaper cause: a write to a private channel the connected account is not a member of fails even with correct scopes, and inviting the account in Slack fixes it without touching the connection.

Ask the agent to diagnose it:

Call slack_get_bot_user and slack_list_all_channels, tell me which workspace and account you are connected as and which channels you can actually see. Then quote the exact error string from the failed call.

Two causes, and neither is a broken connection. The first is membership: private channels are only visible to members, so the agent cannot see one it was never invited to, and inviting the connected account in Slack resolves it immediately. The second is the identifier — Slack tools take channel ids like C0123456789, not the display name, and an agent that passes #general or a name lifted from an example gets channel_not_found rather than a helpful error. Ask it to resolve the name first with slack_find_channels and then use the id from that result.

Ask the agent to diagnose it:

Use slack_find_channels to look up the channel by name and show me the exact channel id you get back. Then retry the failed call with that id.

Sending identity follows the connection: messages post through the authorization you approved, so if a workspace has several ClawLink connections the one marked default is the one used unless the prompt names another. Threading is a separate and more common mistake. A reply belongs in a thread only if the call carries the parent message's timestamp, so an agent that posts without one starts a new message in the channel instead. Ask it to fetch the thread with slack_fetch_message_thread_from_a_conversation first and reply using the ts it returns.

Try reconnecting Slack and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect OpenClaw to Slack: link your Slack account once in the browser and OpenClaw can call the Slack API through 145 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Slack skill from ClawHub, then you click Connect in the dashboard to authorize Slack. OpenClaw calls the tools from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Slack in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Slack working from chat.

No. Connecting through ClawLink uses Slack's OAuth install flow, so you pick the workspace, review the permissions on Slack's own screen, and approve. There is no app to create in api.slack.com, no bot token or app-level token to copy, and nothing to add to openclaw.json. The practical difference shows up later: a token pasted into a config file keeps working until someone remembers to revoke it, whereas a workspace admin removing the app cuts access immediately.

Those are different products for a different job. A no-code platform runs workflows on its own infrastructure and gives you a builder to configure them; Slack's built-in AI works inside Slack. This integration gives your agent the Slack API as tools, so the reasoning happens wherever OpenClaw runs and the agent decides which calls to make in response to what you asked. That matters when the work spans several systems — searching Slack, then filing an issue, then replying — because there is no workflow to pre-define.

Public channels in the workspace you connected, plus private channels the connected account is a member of. Slack scopes access to membership, so a private channel nobody invited you to is invisible to the agent as well, and the fix is to invite the account to the channel in Slack rather than to change anything in ClawLink. This is the most common cause of an agent reporting that a channel does not exist when you can see it perfectly well in your own sidebar.

The connection is Slack's own OAuth install, so the permissions are named on Slack's approval screen, the agent never handles your password, and a workspace admin can revoke the app at any time from Slack's side while you can disconnect from the ClawLink dashboard. Two practical cautions matter more than the mechanism. First, the agent inherits your reach: it can read what you can read, so connect the account whose access you intend it to have. Second, message content is untrusted input — an agent asked to act on whatever it finds in a channel is acting on text anyone in that channel can write, so keep a human in the loop for anything that sends, deletes, or invites.

The ClawHub skill teaches OpenClaw about Slack, but the calls run through the ClawLink plugin and your connected account. Make sure Slack is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.