-
-
Notifications
You must be signed in to change notification settings - Fork 69k
[Feature/Bug]: Slack Multi-Workspace - Cannot send messages cross-account #8018
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingdedupe:childDuplicate issue/PR child in dedupe clusterDuplicate issue/PR child in dedupe clusterstaleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Summary
When using channels.slack.accounts to connect multiple Slack workspaces, messages are received from both workspaces correctly, but cross-account sending does not work.
Setup
{
"channels": {
"slack": {
"enabled": true,
"botToken": "xoxb-...", // Workspace A (primary)
"appToken": "xapp-...",
"accounts": {
"workspace-b": {
"name": "Workspace B",
"botToken": "xoxb-...",
"appToken": "xapp-..."
}
}
}
}
}Behavior
- ✅ Receiving messages from both workspaces works
- ✅ Replying in the same workspace works (auto-routed)
- ❌ Sending to a channel in Workspace A while in a session triggered from Workspace B fails with
channel_not_found
Expected
The message tool should support an accountId parameter (or similar) to explicitly target a specific workspace account for sends.
Workaround Attempted
Tried using the message tool without specifying accountId, hoping it would fall back to the primary account - still got channel_not_found.
Environment
- Clawdbot version: 2026.1.24-3
- Both workspaces use Socket Mode
- Both apps are installed and have the bot invited to relevant channels
Questions
- Is cross-account sending supported?
- If not, is this planned?
- Any workaround besides running separate gateway instances?
Thanks! 🌻
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingdedupe:childDuplicate issue/PR child in dedupe clusterDuplicate issue/PR child in dedupe clusterstaleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Give feedbackNo fields configured for issues without a type.