Get your Obsy webhook URL
Your per-org New Relic webhook URL is:{orgId} in Settings → Organization.
Create a Webhook destination in New Relic
- In New Relic, go to Alerts → Destinations.
- Click Add destination and choose Webhook.
- Set:
- Name:
Obsy - Endpoint URL: your Obsy webhook URL
- Name:
- Under Custom headers, no additional headers are needed.
- Click Save destination.
Create a Workflow
- Go to Alerts → Workflows and click Add a workflow.
- Set a name (e.g.
Obsy routing). - Under Filter data — optionally restrict which issues trigger the workflow (leave blank for all).
- Under Notify, click Add channel and select the
Obsywebhook destination. - Under Custom payload, use the default JSON template or paste the Obsy-compatible template below.
- Click Activate workflow.
Recommended payload template
Alert payload mapping
| New Relic field | Obsy field |
|---|---|
issueTitle | Alert name |
policyName / conditionName | Description |
state | Status (ACTIVATED → firing, RESOLVED → resolved, ACKNOWLEDGED → acknowledged) |
priority | Severity (CRITICAL → critical, HIGH/MEDIUM → warning, LOW → info) |
entityName | Service name |
labels.environment | Environment |
issueId | annotations.newrelic_issue_id |
issueUrl | annotations.newrelic_issue_url |
Troubleshooting
Workflow fires but Obsy shows no alert
Workflow fires but Obsy shows no alert
Open New Relic’s Workflow log and check for HTTP errors on the delivery. A
400 means the payload is malformed — ensure you’re using the recommended template above.State shows as 'firing' even when acknowledged in New Relic
State shows as 'firing' even when acknowledged in New Relic
New Relic sends a separate
ACKNOWLEDGED state transition. If you don’t see it in Obsy, verify the Workflow is configured to fire on all state changes, not just ACTIVATED.