openclaw - 💡(How to fix) Fix [Bug]: Slack socket mode connects successfully, but public channel events are not received [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#63477Fetched 2026-04-09 07:53:17
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
1
Participants
Timeline (top)
labeled ×2subscribed ×2commented ×1mentioned ×1

Slack DM works, but public channel messages and app mentions are not received by OpenClaw.

Root Cause

Slack DM works, but public channel messages and app mentions are not received by OpenClaw.

Code Example

Relevant evidence:

1. Slack plugin is loaded:
- `@openclaw/slack` status: loaded
- source: `stock:slack/index.js`
- version: `2026.4.8`

2. Slack channel health appears normal:
- Slack: ON / OK
- tokens ok
- accounts 1/1

3. Socket mode connects successfully:
- `slack socket mode connected`

4. DM works, but public channel events do not appear in logs:
- Mentioning the bot in a public Slack channel does not generate inbound Slack event logs
- Public channel messages also do not appear to be received

5. Troubleshooting already attempted:
- `app_mention` enabled
- `message.channels` enabled
- required scopes added
- `allowFrom` removed
- gateway restarted
- OpenClaw updated from 2026.4.5 to 2026.4.8

6. Earlier instability observed during troubleshooting:
- websocket pong timeout warnings
- ECONNRESET on Slack websocket
- plugin load later recovered and Slack plugin now shows as loaded

Example log lines:
- `slack socket mode connected`
- no corresponding public channel inbound event logs after `@Joshua hi`
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Slack DM works, but public channel messages and app mentions are not received by OpenClaw.

Steps to reproduce

  • app_mention enabled in Event Subscriptions
  • message.channels also enabled
  • Bot token scopes include:
    • app_mentions:read
    • channels:history
    • channels:read
    • chat:write
  • App token scope includes:
    • connections:write
  • allowFrom was removed from config
  • Slack plugin is loaded
  • Slack channel status shows OK
  • Socket mode shows connected in logs

Expected behavior

When I mention the bot in a public Slack channel, OpenClaw should receive the event and respond

Actual behavior

  • Slack DM works normally
  • Slack socket mode connects successfully
  • Public channel messages and app mentions do not appear in OpenClaw logs
  • No inbound Slack event seems to be received from public channels

OpenClaw version

2026.04.08

Operating system

mac OS 15.4

Install method

npm global

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> local gateway -> slack socket mode

Additional provider/model setup details

OpenClaw is installed globally via npm on macOS and uses a local gateway on loopback. The effective agent model under test is openai-codex/gpt-5.4. Slack is configured with bot token + app token in Socket Mode. DM works correctly, but public channel events are not received. allowFrom was previously present and then removed during troubleshooting. The issue persists after upgrading OpenClaw from 2026.4.5 to 2026.4.8, restarting the gateway, and confirming that the Slack plugin is loaded and the Slack channel status is OK.

Logs, screenshots, and evidence

Relevant evidence:

1. Slack plugin is loaded:
- `@openclaw/slack` status: loaded
- source: `stock:slack/index.js`
- version: `2026.4.8`

2. Slack channel health appears normal:
- Slack: ON / OK
- tokens ok
- accounts 1/1

3. Socket mode connects successfully:
- `slack socket mode connected`

4. DM works, but public channel events do not appear in logs:
- Mentioning the bot in a public Slack channel does not generate inbound Slack event logs
- Public channel messages also do not appear to be received

5. Troubleshooting already attempted:
- `app_mention` enabled
- `message.channels` enabled
- required scopes added
- `allowFrom` removed
- gateway restarted
- OpenClaw updated from 2026.4.5 to 2026.4.8

6. Earlier instability observed during troubleshooting:
- websocket pong timeout warnings
- ECONNRESET on Slack websocket
- plugin load later recovered and Slack plugin now shows as loaded

Example log lines:
- `slack socket mode connected`
- no corresponding public channel inbound event logs after `@Joshua hi`

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

  • Verify the Slack event subscription settings and ensure that the app_mention and message.channels events are properly configured to send events to OpenClaw.

Guidance

  • Check the Slack event subscription settings to confirm that the app_mention and message.channels events are enabled and configured to send events to the correct endpoint.
  • Review the OpenClaw logs to ensure that there are no errors or warnings related to the Slack plugin or socket mode connection.
  • Verify that the bot token scopes include the necessary permissions, such as app_mentions:read and channels:history, and that the app token scope includes connections:write.
  • Test the Slack event subscription by sending a message in a public channel and checking the OpenClaw logs for an inbound event.

Example

  • No code snippet is provided as it is not clearly supported by the issue.

Notes

  • The issue may be related to the removal of the allowFrom configuration, but this is not explicitly stated.
  • The earlier instability observed during troubleshooting, such as websocket pong timeout warnings and ECONNRESET on Slack websocket, may be related to the issue, but this is not clear.

Recommendation

  • Apply workaround: Verify the Slack event subscription settings and ensure that the necessary events are properly configured to send events to OpenClaw, as the issue may be related to the configuration rather than a version-specific bug.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When I mention the bot in a public Slack channel, OpenClaw should receive the event and respond

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING