# New Relic integrations > Connect New Relic to your tech stack to route alerts, sync incident data, and build DevOps automation pipelines. **Canonical page:** https://tray.ai/connectors/new-relic-integrations/ **Categories:** General automation services, Databases **Documentation:** https://tray.ai/documentation/connectors/service/new-relic ## Overview 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. ## Use cases ### 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. - Reduce mean time to acknowledge (MTTA) by triggering downstream actions the moment a New Relic alert fires - Keep incident routing consistent based on alert severity, service name, or team ownership tags - Automatically attach New Relic chart links and APM data directly into Jira tickets or PagerDuty incidents ### 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. - Eliminate duplicate data entry across incident management platforms - Keep SRE, DevOps, and IT teams working from a single source of truth for incident status - Automatically close or reopen related tickets based on New Relic alert state changes ### 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. - Automate weekly or monthly SLO compliance reports delivered directly to Confluence or email - Give product and business leaders visibility into reliability metrics without needing dashboard access - Track error budget burn rate trends over time in a data warehouse like BigQuery or Snowflake ### 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. - Automatically annotate New Relic charts with deployment events from any CI/CD tool - Correlate error rate spikes with specific commits or pull requests within seconds of deploy - Trigger automated rollback workflows when post-deploy New Relic metrics breach thresholds ### 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. - Automatically compile relevant New Relic traces, metrics, and logs into a single incident brief - Cut cognitive load for on-call engineers during high-stress outages - Refine AI prompts with historical incident data over time to improve RCA accuracy ### 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. - Automatically update public status pages the moment a customer-facing alert fires in New Relic - Reduce inbound support volume by notifying customers before they notice the issue - Sync incident resolution status back to the status page and trigger customer follow-up messaging ### 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. - Route security-tagged New Relic alerts directly to Splunk, Sumo Logic, or your SIEM of choice - Automatically create compliance incident records in ServiceNow or Salesforce for audit trails - Deduplicate and suppress flapping security alerts before they reach on-call engineers ## Templates ### 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. Connectors used: New Relic, PagerDuty, Slack ### 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. Connectors used: New Relic, GitHub ### 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. Connectors used: New Relic, Google Sheets, Gmail ### 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. Connectors used: New Relic, Jira, Slack ### 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. Connectors used: New Relic, Statuspage, HubSpot, SendGrid ### 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. Connectors used: New Relic, OpenAI, Slack, PagerDuty ## Challenges Tray.ai solves ### 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 helps:** 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. ### 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 helps:** 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. ### 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 helps:** 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. ### 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 helps:** 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. ### 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 helps:** 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. ## Agent features ### Query Application Performance Metrics (Data Source) 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. ### Fetch Alert Violations and Incidents (Data Source) 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. ### Retrieve Infrastructure Health Data (Data Source) 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. ### Run NRQL Queries (Data Source) 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. ### Look Up Deployment Markers (Data Source) 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. ### Access Synthetic Monitor Results (Data Source) 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. ### Create Alert Policies and Conditions (Agent Tool) 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. ### Acknowledge or Close Incidents (Agent Tool) 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. ### Create Deployment Markers (Agent Tool) 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. ### Mute Alert Conditions (Agent Tool) 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. ### Send Custom Events (Agent Tool) 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. ### Tag and Manage Monitored Entities (Agent Tool) 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. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/