#Slack Channel configuration
1 messages · Page 1 of 1 (latest)
This looks like a known wizard bug in 2026.4.14, not a Slack-specific token problem.
I checked the source/changelog, and 2026.4.15-beta.1 includes this exact fix:
Setup/providers: guard preferred-provider lookup during setup so malformed plugin metadata with a missing provider id no longer crashes the wizard with
Cannot read properties of undefined (reading 'trim').
So what’s happening is likely:
- Slack channel resolution succeeds
- Setup moves on to provider/model selection
- The wizard hits a plugin/provider entry with a missing
id trim()gets called onundefined, and the wizard crashes
So the “channel resolves successfully but then crashes” part actually fits this bug very well.
Best fix
Upgrade to 2026.4.15-beta.1 or newer, then rerun setup.
Workaround if you need to stay on 2026.4.14
Skip the wizard and add Slack config manually, then restart the gateway.
Docs: https://docs.openclaw.ai/channels/slack
Socket Mode example:
{
channels: {
slack: {
enabled: true,
mode: "socket",
appToken: "xapp-...",
botToken: "xoxb-...",
},
},
}
HTTP mode example:
{
channels: {
slack: {
enabled: true,
mode: "http",
botToken: "xoxb-...",
signingSecret: "your-signing-secret",
webhookPath: "/slack/events",
},
},
}
Then restart:
openclaw gateway restart
If you want, paste:
openclaw --version
openclaw status --all
and I can sanity check the upgrade path or your manual Slack config before you retry.