You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When using any Opsgenie Integration that is separate from the Atlassian Integrations (Jira Software, Jira Service Management, etc.) you only have the ability to send updates to Opsgenie, not from Opsgenie as well. So how do we work around this scenario?
Webhooks allow you to send information to a third-party platform, such as a webserver, as long as the URL is accessible from the Web.
The webhook data includes the alert activity (create, acknowledge, etc.) as well as a subset of alert fields (such as the alert ID, username, alias, etc.) which can also include custom headers to add to the Webhook call.
For your JSM Users to access Opsgenie you can either: