Skip to main content
Use a New Relic Workflow webhook to send Issues to Flashduty On-call. One New Relic Issue maps to one Flashduty alert. Priority changes, Alert Event additions or closures, Issue merges, and closure notifications update that alert.

​
In Flashduty On-call

Create either a dedicated or shared New Relic alert integration and copy its complete Push URL.

​
Configure New Relic

1

Create a webhook destination

  1. In New Relic, go to Alerts → Enrich and Notify → Destinations
  2. Create a Webhook destination named Flashduty
  3. Paste the complete Flashduty integration Push URL into Endpoint URL
2

Create a workflow

Create a Workflow whose Issue filters select the required policies, conditions, entities, or tags. Add the webhook destination. Enable at least Activated and Closed. Also enable Priority changed and Other updates to receive priority changes, Alert Event membership changes, and post-merge snapshots.
3

Configure the payload

Keep issue_id, state, and priority. Flashduty rejects a missing issue_id because a random key cannot correlate later updates and closure.
4

Verify the lifecycle

Open a real Issue and confirm an active Flashduty alert. Change its priority or add another Alert Event and confirm an update on the same alert. Finally close the Issue and confirm the original alert recovers. A test notification proves connectivity only, not lifecycle correlation.

​
Alert Key and Issue merges

Flashduty uses issue_id (issueId) directly as the Alert Key. Titles, priorities, policies, conditions, entities, and incident_ids do not affect it. incident_ids is the list of Alert Events aggregated into the Issue and is stored only as context. For trigger_event=MERGE_REQUEST, Flashduty updates the surviving Issue identified by the payload’s issue_id. This version does not invoke Flashduty’s internal alert merge operation or infer and close a source Issue.

​
Status and severity

New Relic warning thresholds create HIGH priority Alert Events, so HIGH maps to Flashduty Warning. Use an Alert Processing Pipeline for a different mapping.

​
Add custom labels

Add a top-level custom_labels object to send more Workflow variables:
custom_labels accepts at most 50 entries. Use snake_case keys. Strings, numbers, booleans, arrays, and objects are accepted; arrays and objects are stored as JSON strings. Empty values are discarded, built-in labels win collisions, and the final event may contain at most 50 labels. Never send secrets. For the complete variable list, see New Relic Workflow variables.