Hey folks.
I've created an automation that kicks off on a schedule and tries to send a message to a Slack webhook, triggering a Slack Automation Workflow to send a message to a channel.
I've tested that Slack Automation via curl and it works fine to post the message to the channel.
I've tested the Jira Automation, and it works to trigger the Slack Workflow, but the only text that shows up in the channel is whatever text has been defined in the Slack Workflow "send a message to a channel step" and NOT the message from the Jira automation.
To clarify, the Slack Send a message to a channel step has this as the message:
"Test: {message}", where {message} should be the actual message sent by the Jira automation to the webhook. Instead, the channel only receives "Test: ".
So none of the values or information contained within the Jira Automation are landing in Slack, even if I put a really simple plain text message in the Jira Automation like "This is just a test", the only thing that shows up in the channel is "Test: ".
I looked up examples and it doesn't look like any special formatting is required, but I feel like something is missing. Any help would be much appreciated.
Edit Part 2:
It seems like the Jira "Send Message to Slack Channel" just isn't working properly. To simplify I created the following rule:
That's it. That's the entire rule. At 4:04PM, send a message to this webhook with that message.
The webhook is hit, a message shows up, but the actual content of the "Send Slack message" step is empty. "This better work" should show up, but nothing does.
Again, if I curl that same webhook and I'm able to properly format the data it shows up just fine.
I suspect this might be because of the change in how Slack handles webhooks. All the examples and documentation I could find on the Slack side have no reference to setting up Data Variables, as can be seen in my other screenshots below. But again, if I format a curl request with that data value and hit the webhook it shows up in channel fine. I'm assuming the "Jira Send Slack message" action format just doesn't match the Slack webhook anymore.
Edit: Attaching some screenshots.
The Jira Rule:
The Slack "Send a Message to a channel" workflow step configuration:
The Slack "Start with a webhook" configuration:
The Slack automation configuration:
The reason I'm confident this is not a Slack side issue:
When I curl the webhook the message shows up perfectly. It's only when Jira sends the message that it fails to show up, as seen here (the top message is from Jira, lacking the actual "testing" we should see, the bottom message is from my curl request, and correctly shows the "test" content):
PEBCAK.
This was apparently the wrong kind of webhook. The workflow webhook I was trying to use has the format https://hooks.slack.com/triggers
The correct incoming webhook format should be (https://hooks.slack.com/services/), which is created not through a workflow, by following the link in the Jira Send Slack Message configuration.
Hi @DARREN_HENDRICKS ,
Welcome to the community!
It is always good to post some screenshots of your automation and integration setting, it will speed up the help from the community.
Also - have you seen this documentation about connecting Jira with Slack?
br
Lisa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Lisa,
Thanks for the reply. I updated my question with some screenshots that should, I hope, help clarify the problem I'm encountering.
I had previously referred to the documentation you shared but I'm afraid it doesn't seem to address this issue.
Thanks,
Darren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.