Problem

Currently, when an Automation rule contains multiple Slack actions, all Slack actions in that rule are forced to use the same Slack workspace connection. Once a user connects Automation to a Slack workspace (via OAuth), every subsequent Slack action — in the same rule or across rules — defaults to that same connection, with no option to select or connect a different workspace per action.
The "New connection" button does not resolve this: it creates a new connection object, but since there is no workspace picker for Slack, the new connection resolves to the exact same workspace as before.
Use case Customers who operate in multiple Slack workspaces (e.g., separate workspaces per business unit, customer, or internal/external channels) want a single Automation rule to notify two different Slack workspaces — for example, Slack Action 1 posts to Workspace A, and Slack Action 2 posts to Workspace B. This is not currently possible.

Current workaround

None identified other than splitting the notification logic across separate automation rules — which is not always feasible depending on rule triggers/conditions.

Suggested solution

Add a workspace selector to the Slack action configuration (similar to how the Bitbucket action already allows choosing a workspace per connection), so each Slack action within a rule can independently target a different connected Slack workspace.