Overview

Connect NewRelic to Sizemotion to automatically create incidents when your alerts trigger. NewRelic's workflow notifications will send alert data to your team's webhook URL, creating incidents with full alert context including priority, sources, and policy information.

Key Benefits:
  • Native NewRelic alert format - no payload customization
  • Automatic severity mapping from NewRelic priorities
  • Route different alerts to different teams
  • Auto-assign incidents to on-call engineers
  • Prevent duplicate incidents using alert IDs

Prerequisites

Before configuring the integration:

  • API Token - Generate from Admin Settings → API Tokens
  • Team ID - Available in Team Settings → Team Information
  • NewRelic Account - With Workflows feature enabled

Setup Steps

Step 1: Get Your Webhook URL

Each team has a unique webhook URL for routing alerts:

  1. Navigate to Team Settings in your workspace
  2. Locate the Team Information section
  3. Note your Team ID (e.g., 5)
  4. Your webhook URL format: 
    https://sizemotion.com/api/v1/incidents/webhook/newrelic/{TEAM_ID}
Multiple Teams? Create separate webhook destinations in NewRelic for each team to ensure proper alert routing.

Step 2: Create API Token

  1. Go to Admin Settings → API Tokens
  2. Click Create New Token
  3. Name it descriptively (e.g., "NewRelic Production")
  4. Save the token securely - it won't be shown again!

Step 3: Configure NewRelic Workflow

In your NewRelic account:

  1. Navigate to Alerts & AI → Workflows
  2. Click Add a workflow
  3. Configure the workflow:
    • Name: Sizemotion Backend Team (or your team name)
    • Filter data: Configure which alerts trigger this workflow
  4. Click Add destination
  5. Select Webhook
  6. Configure the webhook:
    • Name: Sizemotion Backend
    • Endpoint URL: Your webhook URL from Step 1
    • Custom headers: 
      Authorization: Bearer YOUR_API_TOKEN
    • Payload: Use default NewRelic issue format
  7. Test the destination to verify connectivity
  8. Save the workflow
💡 Pro Tip: Create descriptive workflow names like Sizemotion - Backend Critical, Sizemotion - Frontend Warnings to easily identify routing in your NewRelic setup.

Step 4: Test the Integration

Verify your setup:

  1. Use NewRelic's Test destination button to send a test payload
  2. Check your Sizemotion workspace for the test incident
  3. Verify alert metadata appears correctly in incident details

Alert Routing to Teams

Team-Specific Workflows

Create separate workflows for different teams based on alert criteria:

Backend Team Workflow:
  Filter: tags.team = "backend" OR tags.service LIKE "api-%"
  Destination: https://sizemotion.com/api/v1/incidents/webhook/newrelic/5

Frontend Team Workflow:
  Filter: tags.team = "frontend" OR tags.service LIKE "web-%"
  Destination: https://sizemotion.com/api/v1/incidents/webhook/newrelic/8

Priority Mapping

NewRelic priorities automatically map to incident severities:

NewRelic Priority Incident Severity Description
Critical Sev 1 Service down / Critical impact
High Sev 2 Major degradation
Medium Sev 3 Minor issues / Default
Low / Info Sev 4 Informational

Common Scenarios

APM Application Errors (Backend Team)

Workflow Name: Sizemotion Backend - APM Errors
Filter Conditions:
  - Policy name CONTAINS "Production APM"
  - Priority = Critical OR High
  - Source = APM

Destination: Backend Team Webhook
URL: https://sizemotion.com/api/v1/incidents/webhook/newrelic/5

Infrastructure Alerts (DevOps Team)

Workflow Name: Sizemotion DevOps - Infrastructure
Filter Conditions:
  - Policy name CONTAINS "Infrastructure"
  - Tags.environment = production
  - Source = Infrastructure

Destination: DevOps Team Webhook
URL: https://sizemotion.com/api/v1/incidents/webhook/newrelic/12

Browser Monitoring (Frontend Team)

Workflow Name: Sizemotion Frontend - Browser
Filter Conditions:
  - Source = Browser
  - Priority = Critical OR High
  - Page URL CONTAINS "app.yoursite.com"

Destination: Frontend Team Webhook
URL: https://sizemotion.com/api/v1/incidents/webhook/newrelic/8

Troubleshooting

Webhook Not Creating Incidents

Check these common issues:

  • Authorization Header: Verify the API token is correct with "Bearer " prefix
  • Team ID: Ensure the team ID in the URL matches your actual team
  • API Token Permissions: Token must have incidents:create permission
  • URL Format: Should be /api/v1/incidents/webhook/newrelic/{team_id}
  • Workflow Status: Verify the workflow is active in NewRelic

Duplicate Incidents

Duplicate prevention is automatic using NewRelic's incident ID:

  • Same issue triggering multiple times creates only one incident
  • Issue updates don't create new incidents (feature coming soon)
  • Different issues always create separate incidents

Missing Alert Data

If incident details are incomplete:

  • Verify you're using NewRelic's default issue format (not custom payload)
  • Check that required fields (incident_id, title) are present
  • Review the incident metadata for all available NewRelic fields

Testing Your Webhook

To validate the integration:

  1. Use NewRelic's Test destination feature in the workflow
  2. Temporarily lower alert thresholds to trigger a real alert
  3. Check incident details to verify all metadata is captured
  4. Verify tags include sources and policy names

Getting Help

If issues persist:

  • Check Admin Settings → API Tokens for recent activity
  • Review NewRelic Workflows → Destinations for error messages
  • See API Documentation for technical details
  • Contact your workspace administrator
✅ Integration Complete! Your NewRelic alerts will now automatically create incidents with full context. Configure workflows to route different alert types to the appropriate teams.

Next Steps