New Relic connector
Automate Observability Workflows with New Relic Integrations
Connect New Relic to your tech stack to route alerts, sync incident data, and build DevOps automation pipelines.
What can you do with the New Relic connector?
New Relic gives you real-time performance monitoring, distributed tracing, and alerting across your application stack. But that telemetry data only gets useful when it reaches your incident management, collaboration, and BI tools. With tray.ai, teams can automate the full incident lifecycle — from a New Relic alert firing through to resolution, retrospective, and reporting — without writing custom glue code.
Automate & integrate New Relic
Automating New Relic business process or integrating New Relic data is made easy with tray.ai
Use case
Automated Incident Response and Escalation
When New Relic detects an anomaly or breaches an alert threshold, tray.ai can instantly create incidents in PagerDuty or Opsgenie, post notifications in Slack, and open tickets in Jira — all in parallel. That eliminates the manual triage step that costs precious minutes during outages and ensures no critical alert gets missed.
Use case
Bi-Directional Incident Sync Across Tools
Engineering teams often manage incidents simultaneously in New Relic, ServiceNow, and Jira, which leads to fragmented status updates. tray.ai keeps incident state in sync across platforms — when a ServiceNow ticket is resolved, the corresponding New Relic alert policy acknowledgment updates automatically, and vice versa.
Use case
SLO and Error Budget Reporting to Business Stakeholders
New Relic tracks SLOs and error budgets, but getting that data to non-technical stakeholders usually means manual exports and spreadsheet work. tray.ai can pull SLO compliance data from New Relic's NerdGraph API on a schedule and push formatted summaries into Google Sheets, Confluence, or Tableau dashboards.
Use case
Deployment Marker and Change Tracking Automation
Correlating deploy events with New Relic APM data is how you understand what a release actually did to performance. tray.ai can automatically post deployment markers to New Relic whenever a CI/CD pipeline in GitHub Actions, CircleCI, or Jenkins completes, giving you instant correlation between releases and performance regressions.
Use case
AI Agent-Driven Root Cause Analysis Assistance
Build AI agents on tray.ai that query New Relic's NerdGraph API to gather APM traces, infrastructure metrics, and log data when an incident fires, then pass that context to an LLM like OpenAI to generate a preliminary root cause analysis summary. On-call engineers get a head start before they even open their laptops.
Use case
Customer-Impacting Incident Communication
When New Relic identifies a customer-facing service degradation, tray.ai can automatically trigger status page updates in Statuspage.io or Atlassian Status Page, and send proactive email or SMS notifications to affected customer segments from your CRM. Support ticket volume stays down and customers stay informed.
Use case
Security and Compliance Alert Routing
New Relic's security monitoring and infrastructure alerting can detect anomalous traffic patterns, unauthorized access attempts, or compliance violations. tray.ai routes these alert types to your SIEM, security Slack channels, or compliance tracking systems in real time, keeping security and engineering workflows cleanly separated.
Build New Relic Agents
Give agents secure and governed access to New Relic through Agent Builder and Agent Gateway for MCP.
Data Source
Query Application Performance Metrics
Retrieve real-time and historical performance data — response times, throughput, error rates — for monitored applications. An agent can use this to spot bottlenecks or generate health summaries.
Data Source
Fetch Alert Violations and Incidents
Pull active or historical alert violations and incidents from New Relic to give an agent situational awareness during an outage. This enables automated triage by surfacing which thresholds have been breached and for how long.
Data Source
Retrieve Infrastructure Health Data
Access CPU, memory, disk, and network metrics for monitored hosts and containers. An agent can use this to correlate infrastructure issues with application-level degradation.
Data Source
Run NRQL Queries
Execute custom NRQL queries against telemetry data to surface specific insights on demand. This gives an agent flexible, ad-hoc access to logs, traces, events, and metrics across any monitored service.
Data Source
Look Up Deployment Markers
Retrieve recorded deployments and change markers to correlate performance shifts with recent code releases. An agent can use this to automatically determine whether a new deployment caused a detected anomaly.
Data Source
Access Synthetic Monitor Results
Fetch results and failure details from New Relic Synthetic monitors that simulate user interactions. An agent can use this to flag external availability issues before real users are impacted.
Agent Tool
Create Alert Policies and Conditions
Programmatically define new alert policies and threshold conditions for monitored entities. An agent can use this to automatically set up monitoring when a new service is deployed or an on-call policy changes.
Agent Tool
Acknowledge or Close Incidents
Update the status of open incidents by acknowledging or resolving them directly within New Relic. This lets an agent coordinate incident response workflows and cut noise once a fix has been confirmed.
Agent Tool
Create Deployment Markers
Record deployment events against an application to mark when a new version was released. An agent can trigger this automatically as part of a CI/CD pipeline, making before-and-after performance comparisons straightforward.
Agent Tool
Mute Alert Conditions
Apply muting rules to suppress alerts during planned maintenance windows or known incidents. An agent can automate this to prevent alert fatigue when a scheduled downtime or controlled change is underway.
Agent Tool
Send Custom Events
Ingest custom event data into New Relic's telemetry pipeline to capture business or operational events that aren't natively tracked. An agent can use this to enrich observability data with context from external systems like CRMs or ticketing tools.
Agent Tool
Tag and Manage Monitored Entities
Add, update, or remove metadata tags on monitored services, hosts, and applications. An agent can keep entity metadata consistent across environments, making it easier to filter and query data by team, environment, or product area.
Get started with our New Relic connector today
If you would like to get started with the tray.ai New Relic connector today then speak to one of our team.
New Relic Challenges
What challenges are there when working with New Relic and how will using Tray.ai help?
Challenge
NerdGraph API Complexity and NRQL Query Building
New Relic's primary API is NerdGraph, a GraphQL API that requires teams to construct complex nested queries and understand NRQL syntax to extract meaningful data. For engineers who aren't GraphQL specialists, this creates a real learning curve that slows down integration work.
How Tray.ai Can Help:
tray.ai's New Relic connector abstracts common NerdGraph operations into pre-built actions, while the flexible HTTP client lets advanced teams execute raw NerdGraph queries with full variable support. Both low-code users and developers can work with New Relic data without becoming GraphQL experts.
Challenge
Alert Noise and Deduplication at Scale
High-traffic applications can generate hundreds of New Relic alerts per day, overwhelming on-call teams with redundant notifications across Slack, PagerDuty, and email. Without filtering and deduplication logic, engineers spend more time managing alerts than resolving incidents.
How Tray.ai Can Help:
tray.ai workflows can implement conditional logic to filter, deduplicate, and group New Relic alerts before routing them downstream. Teams can define rules based on alert severity, entity tags, time-of-day, or previous alert state to ensure only actionable notifications reach engineers.
Challenge
Connecting Observability Data to Business Context
New Relic captures deep technical telemetry, but mapping that data back to business impact — which customers are affected, what revenue is at risk, which SLAs are threatened — requires pulling data from CRMs, billing systems, and contract databases that New Relic doesn't connect to natively.
How Tray.ai Can Help:
tray.ai bridges New Relic and business systems like Salesforce, HubSpot, and Stripe. When a critical alert fires, workflows can automatically enrich the incident with customer impact data by joining New Relic service tags to customer account records in real time.
Challenge
Maintaining Audit Trails for Compliance and Post-Mortems
Regulated industries and mature engineering orgs need comprehensive audit trails of every alert, acknowledgment, escalation, and resolution. New Relic's native retention policies may not meet long-term compliance requirements, and manually exporting incident history is time-consuming.
How Tray.ai Can Help:
tray.ai can automatically stream every New Relic alert event to a data warehouse like Snowflake, BigQuery, or a Splunk index in real time, creating a durable and queryable incident history. This supports both compliance audits and data-driven post-mortem analysis without manual data exports.
Challenge
Multi-Account and Multi-Environment Alert Management
Large enterprises often run separate New Relic accounts for production, staging, and different business units, which makes it hard to get a unified view of system health and consistently apply alert routing logic across all environments.
How Tray.ai Can Help:
tray.ai supports multiple authenticated New Relic connections within a single workflow, so teams can build centralized alert routing pipelines that pull data from multiple accounts. Conditional branching logic ensures each alert is handled according to its originating environment and business unit without duplicating workflows.
Talk to our team to learn how to connect New Relic with your stack
Find the tray.ai connector with one of the 700+ other connectors in the tray.ai connector library to integrate your stack.
Integrate New Relic With Your Stack
The Tray.ai connector library can help you integrate New Relic with the rest of your stack. See what Tray.ai can help you integrate New Relic with.
+Slack & New Relic
Learn how to integrate Slack and New Relic together
+PagerDuty & New Relic
Learn how to integrate PagerDuty and New Relic together
+OpsGenie & New Relic
Learn how to integrate OpsGenie and New Relic together
+Jira & New Relic
Learn how to integrate Jira and New Relic together
Start using our pre-built New Relic templates today
Start from scratch or use one of our pre-built New Relic templates to quickly solve your most common use cases.
Template
New Relic Alert to PagerDuty Incident with Slack Notification
Automatically creates a PagerDuty incident and posts an enriched Slack message with service context whenever a New Relic critical alert fires, then closes the PagerDuty incident when the alert resolves.
Steps:
- Receive New Relic alert webhook payload including alert condition, entity name, and severity
- Create a new PagerDuty incident with full alert context and link to New Relic entity page
- Post a formatted Slack message to the relevant team channel with incident details and PagerDuty link
- Listen for New Relic alert resolved event and automatically acknowledge and resolve the PagerDuty incident
Connectors Used: New Relic, PagerDuty, Slack
Template
CI/CD Deployment Marker Sync to New Relic
Posts a deployment marker to New Relic APM automatically whenever a GitHub Actions workflow completes, tagging the deploy with commit SHA, author, and environment for instant performance correlation.
Steps:
- Trigger on GitHub Actions workflow_run completion event for production deployments
- Extract commit SHA, author email, repository name, and deployment environment from the GitHub payload
- Call New Relic NerdGraph API to record a deployment marker against the matching APM application entity
- Post a confirmation message to a Slack deployments channel with a direct link to the New Relic deploy view
Connectors Used: New Relic, GitHub
Template
Weekly SLO Compliance Report to Google Sheets
Queries New Relic NerdGraph on a weekly schedule to retrieve SLO compliance percentages and error budget remaining for all tracked services, then appends results to a Google Sheet for stakeholder reporting.
Steps:
- Trigger on a weekly schedule every Monday morning before standup
- Execute a NerdGraph NRQL query to retrieve SLO compliance and error budget burn rate for each service
- Append a new timestamped row to a Google Sheet tracking SLO performance over time
- Send a Gmail digest to engineering leadership and product managers with the week's SLO summary
Connectors Used: New Relic, Google Sheets, Gmail
Template
New Relic Alert to Jira Bug Ticket with Auto-Assignment
Creates a Jira bug ticket automatically when a New Relic alert fires, enriches it with APM data and a link to the relevant New Relic dashboard, and assigns it to the correct team based on the alert's service tag.
Steps:
- Receive New Relic alert webhook and parse service name, environment, and alert condition details
- Look up the Jira team assignment mapping based on the New Relic service entity tag
- Create a Jira bug with pre-populated description including NRQL query link, alert threshold, and current metric value
- Post a Slack notification to the assigned team channel linking to both the Jira ticket and New Relic alert
Connectors Used: New Relic, Jira, Slack
Template
New Relic Incident to Statuspage and Customer Email Notification
Detects customer-facing service degradations in New Relic and automatically creates a Statuspage incident while triggering a proactive email to affected customers sourced from a CRM segment.
Steps:
- Receive New Relic webhook for alerts tagged as customer-facing services
- Create a new incident on Statuspage with the appropriate affected component and impact level
- Query HubSpot for contacts with active subscriptions to the impacted service
- Send a proactive service disruption email via SendGrid and update Statuspage when the alert resolves
Connectors Used: New Relic, Statuspage, HubSpot, SendGrid
Template
AI-Powered On-Call Incident Brief Builder
When a critical New Relic alert fires, automatically queries related traces, error logs, and infrastructure metrics, then generates an AI-written incident summary and posts it to the incident Slack channel.
Steps:
- Trigger on New Relic critical alert webhook and extract the affected entity GUID and alert condition
- Execute multiple NerdGraph queries to collect recent error traces, top error messages, and infrastructure host metrics
- Pass the collected telemetry data to OpenAI with a prompt to generate a concise root cause hypothesis and recommended investigation steps
- Post the AI-generated incident brief to the Slack incident channel and attach it as a note on the PagerDuty incident
Connectors Used: New Relic, OpenAI, Slack, PagerDuty