Bug Report: Slack Channel Selection in Automations Does Not Support Multiple Workspaces

[Takesuz (Takeshi Suzuki)]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Summary: When multiple Slack workspaces are connected to Cursor, only the channels from one workspace are available for selection in Automations (both for the “Slack: New message” trigger and the “Send to Slack” tool).

Steps to Reproduce:

Connect two or more Slack workspaces via Cursor Integrations dashboard.
Create a new Automation and select a Slack-related trigger or the “Send to Slack” tool.
Open the channel selection dropdown.
Expected Behavior: Channels from all connected Slack workspaces should be available for selection.

Actual Behavior: Only channels from one workspace (likely the most recently connected one) are displayed. Channels from other workspaces are not selectable.

Impact:

It is not possible to configure Automations targeting channels in non-listed workspaces.
Slack notifications sent via Automations also fail for the non-listed workspaces, making reconnection an ineffective workaround.
Environment:

Multiple Slack workspaces connected to Cursor
Affected features: Automations (Slack trigger and Send to Slack tool)

Steps to Reproduce

Connect two or more Slack workspaces via Cursor Integrations dashboard.
Create a new Automation and select a Slack-related trigger or the “Send to Slack” tool.
Open the channel selection dropdown.
Expected Behavior: Channels from all connected Slack workspaces should be available for selection.

Operating System

Windows 10/11

Version Information

Affected features: Automations (Slack trigger and Send to Slack tool)

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report.

Right now, the Slack integration in Cursor only supports connecting one workspace per user. If you connect a second workspace, it replaces the previous one, so the channel dropdown only shows channels from the most recently connected workspace. This is a current limitation, not a bug.

As a workaround, you can reconnect the workspace you need before setting up a specific automation. It’s not ideal, but it’s the only option for now.

I’ve shared the request for multi-workspace support with the team. There’s no timeline yet, but your report helps with prioritization, especially given the team size.

Let me know if you’ve got any other questions.

[Takesuz (Takeshi Suzuki)]

Thank you . I got it

Note that this isn’t just a setup issue; it happens when the automation actually runs. You can see the Slack error in the attached image.