Send automation to various slack channels based on custom field selection

[Sheri Seldes]

I have a custom field (customfield_14543) with dropdown selections of Team 1, Team 2, Team 3, etc.  When Team 1 is selected in the custom field, the automation will send a message to Team 1's slack channel.  

When the custom field value changes (trigger) do I need to use Advanced Branching to send a slack message to that team?

[Jayesh Raghuvanshi]

@Sheri Seldes 

No—Advanced Branching is not needed for this single-select dropdown use case in Jira Cloud; use a “Field value changed” trigger with an If/else block to route a “Send Slack message” action to the correct channel based on the selected team

Setup Steps

• Trigger: Add “Field value changed” and monitor the Team custom field (customfield_14543) so the rule fires whenever that dropdown changes
• Routing: Add an If/else block, and in each branch use an Issue fields condition like “Team equals Team 1,” “Team equals Team 2,” etc., to direct the flow per team value
• Slack action: In each branch, add “Send Slack message,” connect Slack via an incoming webhook, and set the “Channel or user” target (for example, #team-1) along with the message body
• Message content: Use smart values in the Slack message body to include details like {{issue.key}}, {{issue.summary}}, and other fields for context

Dynamic channel mapping

• Channel override caveat: The “Channel or user” override in the Slack action only works reliably with Slack’s legacy incoming webhooks; with newer app webhooks it posts to the webhook’s bound channel, so a single webhook cannot be reused to dynamically switch channels at runtime
• Practical patterns: If each team has its own Slack channel, either create one branch per team with its own Slack action/webhook, or maintain separate actions configured to the correct channel within the If/else block
• Fully dynamic alternative: Use the “Send web request” action to call Slack’s chat.postMessage API with a bot token, passing the channel ID that corresponds to the selected team, which allows true per-issue dynamic channel selection and advanced formatting/threads

Thanks
Jayesh R

[Duc Thang TRAN]

Hello @Sheri Seldes 

I don’t use Slack myself, but according to my research, it seems that Slack channels follow this format:
https://app.slack.com/client/(workspace_id)/(channel_id)

So it’s possible to use a dynamic value if your custom field stores the Slack channel ID and here the various : {{fieldChange.toString}}
eg : https://app.slack.com/client/(workspace_id)/{{fieldChange.toString}}

However, I think it’s not very user-friendly for Jira users to have to select a channel ID instead of a channel name.

Hope this helps