Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to Extract Custom Fields and Data into an Alert

This article outlines how to extract fields and data into an alert that are not offered through an integration by default.

The Advanced tab of an integration shown below is only available only on the standalone Opsgenie Standard and Enterprise plans, and the JSM/O Premium and Enterprise plans.

These methods can still be applied to extract fields and data into the tags or extra properties fields on the Opsgenie Free and Essentials plans, and the JSM/O Free and Standard plans:



If a field and/or data is being parsed in the payload, it can be extracted into an alert using string processing or regular expressions (regex).


Each Opsgenie integration offers a number of draggable dynamic fields. These can be added into an alert to parse data and construct rich, informative, customized alerts.

Some 3rd party sources send custom fields to Opsgenie which are not offered through an integration by default. As long as the field is being parsed in the payload, it can be extracted into Opsgenie alert fields using string processing or regex.


Where to check:

If a field is not parsed into an alert as expected, check the Logs Tab to review whether or not it was parsed in the payload. 

Logs can be searched by timestamp and/or strings. Specifically the Processed incomingData and Received integration request logs will show what data is being parsed in the payload:



With some integrations such as Jira and JSM, workflows require custom fields to be entered when creating an issue. These custom fields are not included by default in the Jira and JSM integrations, but still parse in the payload of the alert:



Note - There are some limits to the Logs where data parsed can be truncated:



With cases like this it’s best to extract the entire payload into the alert’s description field (which has a max character limit of 15000 characters). This can be done under the Advanced tab of an integration using {{_payload}} to determine if the custom field is being parsed in the payload, and can then be extracted into the alert:




Leveraging a JSON formatter can be an easier way to understand the formatting of how a field is being parsed:



As shown above, the custom field is nested. A dynamic field such as:


can then be used to extract the value into an alert field(s): 



* Since Jira, JSM and other integrations format data and custom fields differently through nesting, lists, arrays, webhook URL, headers, etc. it depends on how the field is being parsed in the payload.

Again - as long as a field and/or data is being parsed in the payload, it can be extracted into the alert using string processing or regex:




In regard to Jira and JSM, customers have leveraged some of these options to extract a custom field:

Legacy Integration:







Cloud Integration:






Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 15, 2022

* Zendesk is one example of an integration that parses data different than Jira and JSM.

Instead of parsing data through {{_payload}}, Zendesk parses the payload in the _httpParams or {{_url}} object:



To extract a custom field such as the requester_email above, I could use a string processing method such as {{_url.ticket.substringBetween("requester_email:"," |") }}.

This custom field is included in the entirety of the ticket field, which is also nested under the _httpParams or {{_url}}:



Documentation: Using Raw Parameters From Webhook Url, Payload and Headers

Like Patricia Francezi likes this

@Nick H Where can I find a list of possible operations for alert fields template? Like the `extract` and `substringBetween` functions, I would like to see a full list of operations that are possible for alert field values.


EDIT: Nevermind, I just found the link on your last comment :facepalm:

Like Nick H likes this

@Nick H Thank you very much for the tips. I was trying to get the tags details from an integration request under _httpParams and with your technique, it works perfectly ! 

Like Nick H likes this


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events