Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-1309

Channel or user override not working in the "Send Slack Message" action

XMLWordPrintable

    • Severity 3 - Minor
    • Jira Software, Jira Service Management

      Issue Summary

      The option of overring a Slack channel or user in the "Send Slack message" action in Automation is not working when using an incoming webhook configured with the current method suggested by Slack:

      However, the override works if the incoming webhook is setup with the method recommended in the Automation action. However, there is a notice on that Slack page mentioning that it is a legacy and outdated method that will be deprecated soon:

      Steps to Reproduce

      1. Configure an incoming webhook using the suggested method by Slack: https://api.slack.com/messaging/webhooks
      2. In the automation action "Send Slack message", add a Channel or user override.

      Expected Results

      The channel or user override should work with the current version of the Slack process for configuring incoming webhooks. 

      Actual Results

      The channel or user override only works with the legacy method of generating an incoming webhook in Slack.

      Workaround

      If possible, use the legacy Incoming Webhooks Slack app.

        1. image-2024-06-06-16-01-33-196.png
          image-2024-06-06-16-01-33-196.png
          92 kB
        2. image-2024-06-06-16-04-26-747.png
          image-2024-06-06-16-04-26-747.png
          170 kB

            [AUTO-1309] Channel or user override not working in the "Send Slack Message" action

            Pinned comments

            Pinned by Rebecca Smith

            Simmo added a comment -

            This isn't a bug. The automation send slack message action is only designed to work with the legacy webooks and not the newer APIs suggested by Slack.

            Simmo added a comment - This isn't a bug. The automation send slack message action is only designed to work with the legacy webooks and not the newer APIs suggested by Slack.

            All comments

            Nahuel Rodríguez added a comment -

            Hello, 

            Slack already warned about legacy webhooks to be deprecated sometime in the future. Is there any plan to improve this, given that?

            https://api.slack.com/legacy/custom-integrations/messaging/webhooks

            Thanks

            Nahuel Rodríguez added a comment - Hello,  Slack already warned about legacy webhooks to be deprecated sometime in the future. Is there any plan to improve this, given that? https://api.slack.com/legacy/custom-integrations/messaging/webhooks Thanks

            Pinned by Rebecca Smith

            Simmo added a comment -

            This isn't a bug. The automation send slack message action is only designed to work with the legacy webooks and not the newer APIs suggested by Slack.

            Simmo added a comment - This isn't a bug. The automation send slack message action is only designed to work with the legacy webooks and not the newer APIs suggested by Slack.

            Mikael Sandberg added a comment -

            The workaround if using the legacy app is not possible is to use a web request and send the message to the chat.postMessage endpoint. The channel argument can either be a channel, private group or member ID for DMs.

            Mikael Sandberg added a comment - The workaround if using the legacy app is not possible is to use a web request and send the message to the chat.postMessage endpoint. The channel argument can either be a channel, private group or member ID for DMs.

              Unassigned Unassigned
              ad5abbdc65b1 Marco Velasco
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: