Overview
Easyalert automatically detects and processes webhooks from New Relic Workflows.New Relic Workflows is the recommended method for new integrations. Classic
Alerts is deprecated but still supported.
Requirements
- New Relic account (One platform)
- Easyalert account and active tenant
- Access to Alerts & AI → Workflows in New Relic
Setup Instructions
1
Create Integration in Easyalert
- Go to Integrations page from left menu
- Click Add Integration button
- Select New Relic as Source Type
- Enter a name (e.g.,
New Relic Production) - Click Create to save
- Copy the generated Webhook URL
Example: https://api.easyalert.io/api/v1/webhooks/ingest/wh_abc123...
2
Create Workflow in New Relic
Go to Alerts & AI → Workflows → Add a workflow
3
Create Webhook Destination
- In Notify section, select Webhook
- Click Create new destination
- Paste Easyalert Webhook URL as Endpoint URL
4
Configure Payload Template
Use this recommended payload:
NOTE: Handlebars syntax uses{{ }}. The{{ json ... }}helper produces JSON-safe output.
5
Test the Integration
Use the Send test notification feature in New Relic
Handlebars Variables
New Relic Workflows use Handlebars syntax:Field Mapping
State and Severity Mapping
Status Mapping
Severity Mapping
Trigger Events
Custom Field → Tag Conversion
All custom fields you add to the template are automatically captured as tags.Example
Template:Routing Examples
Escalation Routing:Workflow Filter Examples
Critical Issues Only
Specific Policies
Specific Entity Types
Test
Recovery Test
Classic Alerts Setup (Legacy)
For legacy New Relic alerts:1
Create Notification Channel
- Go to Alerts → Notification channels 2. Click New notification channel 3. Select Webhook
2
Configure Webhook
- Channel name: Easyalert - Base URL: Your Easyalert webhook URL
3
Add to Policies
- Go to your alert policy 2. Add the webhook channel to notification settings
Classic Alerts Field Mapping
Troubleshooting
Webhooks not being received
Webhooks not being received
- Test destination from New Relic UI
- Verify workflow filter matches your issues
- Check workflow is enabled
- Verify destination URL is correct
Invalid JSON error
Invalid JSON error
- Use
{{ json ... }}helper for proper formatting - Verify Handlebars template syntax
- Check field names match New Relic schema
- Test with simplified payload first
Issues not auto-resolving
Issues not auto-resolving
- Verify CLOSED state triggers workflow
- Check
issueIdmatches between states - Ensure workflow sends on all state changes
Wrong priority mapping
Wrong priority mapping
- Check priority field in payload
- Configure custom severity mapping
- Verify priority is set on alert conditions
Best Practices
Use Workflows
Use Workflows
Migrate to Workflows for better control and flexibility over Classic Alerts.
Include Entity Data
Include Entity Data
Add
entitiesData.names to identify affected infrastructure or services.Set Proper Priorities
Set Proper Priorities
Configure priority on your alert conditions for accurate severity mapping.
Add Custom Fields for Routing
Add Custom Fields for Routing
Include
customer, team, environment in payload for escalation routing.Include Runbook URLs
Include Runbook URLs
Add runbook links in alert conditions for quick remediation access.

