Description
We are facing issues when trying to integrate the Slack MCP specifically in the Deco.cx workspace.
- In other workspaces, the integration works as expected.
- When connecting the same agent to a different workspace, it also works fine.
- However, in the Deco.cx workspace, the bot does not recognize messages and does not respond.
It seems that the teamId is being returned as empty, as if the OAuth flow is not working correctly only for this workspace.
Steps to Reproduce
- Connect Slack MCP to the Deco.cx workspace.
- Try interacting with the bot.
- Notice the bot does not respond.
- Compare with the same integration in another workspace (works fine).
Expected Behavior
The bot should recognize and respond to messages in the Deco.cx workspace, just like it does in other workspaces.
Actual Behavior
- The
teamId seems to be returned as empty.
- The bot does not recognize any messages.
- OAuth does not appear to complete correctly only in this workspace.
Evidence
- Test performed on 2025-09-19 (see attached screenshot).
- The screenshot shows the agent working fine in another workspace.
Environment
- Test date: 2025-09-19
- Affected workspace: Deco.cx
- Other workspaces: working as expected
Description
We are facing issues when trying to integrate the Slack MCP specifically in the Deco.cx workspace.
It seems that the
teamIdis being returned as empty, as if the OAuth flow is not working correctly only for this workspace.Steps to Reproduce
Expected Behavior
The bot should recognize and respond to messages in the Deco.cx workspace, just like it does in other workspaces.
Actual Behavior
teamIdseems to be returned as empty.Evidence
Environment