Incident Ingest

New Relic + Alert24 Integration: Forward Alerts as Incidents

Forward New Relic alert notifications to Alert24 using a webhook destination and message template. Covers destination setup, Jinja template, and deduplication.

New Relic's notification system supports webhook destinations that POST alert payloads to any URL. Combined with a Jinja2 message template, you can send properly formatted incident data directly to Alert24.

Before you start

You'll need:

  • An Alert24 API key with write or incidents scope (Settings → API Keys)
  • New Relic account with alerts configured (New Relic One / New Relic Alerts)

Create a webhook destination

  1. In New Relic, go to Alerts & AI → Destinations
  2. Click + Add destination → Webhook
  3. Set Destination name to Alert24 Incidents
  4. Set Endpoint URL to https://app.alert24.net/api/v1/incidents
  5. Under Custom headers, add:
    • Authorization: Bearer ak_live_YOUR_KEY
    • Content-Type: application/json
  6. Click Save destination

Create a notification channel

  1. Go to Alerts & AI → Notification channels
  2. Click + Add channel
  3. Set Channel name to Alert24
  4. Select your Alert24 Incidents destination
  5. Set the Message template to:
    {
      "title": "{{ issueTitle }}",
      "description": "{{ annotations.description.[0] | default: '' }}",
      "severity": "{{ if eq priority 'CRITICAL' }}critical{{ else if eq priority 'HIGH' }}high{{ else if eq priority 'MEDIUM' }}medium{{ else }}low{{ end }}",
      "alias": "newrelic-{{ issueId }}",
      "source": "newrelic",
      "tags": ["newrelic", "{{ accumulations.policyName.[0] | default: '' }}"]
    }
    
  6. Click Save channel

Attach to a policy

  1. Go to Alerts & AI → Alert policies
  2. Open an existing policy or create a new one
  3. Under Notification channels, click Add notification channels
  4. Select your Alert24 channel
  5. Save

New Relic will POST to Alert24 whenever an issue opens under this policy.

Deduplication

The alias uses New Relic's issueId — a stable identifier for the lifetime of an issue. Repeated notifications for the same open issue increment the Alert24 occurrence count rather than opening new incidents.

Tips

  • New Relic One workflows: If you use New Relic's newer Workflows feature (under Alerts & AI → Workflows), create a workflow that triggers on issue creation and sends to your Alert24 webhook destination directly — the same destination and template work.
  • Template syntax: New Relic message templates use Handlebars-like syntax. Test the payload with New Relic's built-in Send test notification button before attaching the channel to live policies.
  • Issue vs. incident: New Relic groups individual alert violations into issues. The issueId maps cleanly to Alert24's alias for deduplication.