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

OpsGenie Webhook Integration with V2 API

Hey folks,

I am migrating New Relic Notification Channels to Workflows and I have a webhook payload for OpsGenie V2 API KEY integration. 

Most of the values are coming through but the hard-coded one is not. I put it in bold. 

In OpsGenie, I wanted this value to be in the Entity Field. How can I do that? How should I put it? I've been wrapping up my head around this, please help :( 

"issue_id": {{ json issueId }},
"message": {{ json annotations.title.[0] }},
"details": {
"self_url": {{ json issuePageUrl }},
"state": {{ json state }},
"is_correlated": {{ json isCorrelated }},
"created_at": {{ createdAt }},
"updated_at": {{ updatedAt }},
"activated_on": {{ activatedAt }},
"closed_at": {{#if issueClosedAtUtc}} {{ json issueClosedAtUtc }} {{else}}"None"{{/if}}
"incident_ids": "{{#each incidentIds}}{{this}}{{#unless @last}}, {{/unless}}{{/each}}",
"priority": {{#contains "P1" accumulations.policyName.[0]}} "P1" {{else}} {{#contains "P3" accumulations.policyName.[0]}} "P3" {{else}} "P5"{{/contains}} {{/contains}},
"customPriority": {{#contains "P1" accumulations.policyName.[0]}} "P1" {{else}} {{#contains "P3" accumulations.policyName.[0]}} "P3" {{else}} "P5"{{/contains}} {{/contains}},
"owner": "NewRelic",
"impactedEntities": {{json entitiesData.names}},
"totalIncidents": {{json totalIncidents}},
"state": {{ json state }},
"trigger": {{ json triggerEvent }},
"isCorrelated": {{ json isCorrelated }},
"createdAt": {{ createdAt }},
"updatedAt": {{ updatedAt }},
"sources": {{ json accumulations.source }},
"alertPolicyNames": {{ json accumulations.policyName }},
"alertConditionNames": {{ json accumulations.conditionName }},
"workflowName": {{ json workflowName }}

1 answer

1 vote
Nick H Atlassian Team Aug 17, 2022

Hi @Joanne Oliveira ,

Do you know whether or not that field is in fact parsing in the payload? You should be able to check the Logs tab for either the Processed incomingData or Received integration request logs.


If it is found in either of those logs, then you should be able to use some form of string processing or regex to extract it into the alert. Maybe even something like this might work:




You could also try extracting the entire {{_payload}} of the alert into the description field to see if it's found, then use a JSON formatter to help determine exactly what you might need to extract it.


Since it's not a field offered by default within the New Relic integration, it would need to be extracted with some form mentioned above.


This one worked!

Thank you! 

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

208 views 1 6
Read article

Atlassian Community Events