New Relic
Turn incidents and requests into New Relic work items, and keep status in step across your tools.
25 ways to read, 8 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with New Relic, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create alert policyApproval by rule
- Create change eventApproval by rule
- List accountsRead
Example flow
- New Relic · List accountsDone
- New Relic · Create alert policyNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches New Relic.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to New Relic
- New Relic's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a New Relic test account before you go live.
For developers
Technical detail
Search New Relic entities, dashboards, monitors and service levels, read alerts, issues and users, run bounded NRQL, record deployments and manage policies, workloads and tags.
New Relic API docs- Source actions
- 25
- Destination actions
- 8
- Data types
- 22
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Accounts1
- List accountsSource
Accounts the user key can access.
Alert conditions2
- Get NRQL alert conditionSource
One NRQL alert condition by ID.
- List NRQL alert conditionsSource
NRQL alert conditions with their query, thresholds and signal settings.
Alert policies4
- Create alert policyDestinationNot retried automaticallyApproval before production
Creates an alert policy with a name and incident preference.
- Get alert policySource
One alert policy by ID.
- List alert policiesSource
Alert policies in the account with their incident preference.
- Update alert policyDestinationProvider duplicate protectionApproval before production
Renames a policy or changes its incident preference.
Alert workflows1
- List alert workflowsSource
Workflows that route issues to destinations, with filters and channels.
Authentication domains1
- List authentication domainsSource
Authentication domains in the organization (needed to list users and groups).
Change events2
- Create change eventDestinationNot retried automaticallyApproval before production
Records a change tracking event (deployment, feature flag, business or operational event) on an entity.
- List change eventsSource
Deployments and change tracking events recorded on an entity in a bounded time window (NRQL).
Current user1
- Get current userSource
The user that owns the API key.
Dashboards2
- Get dashboardSource
One dashboard with its pages, widgets (NRQL configuration) and variables.
- List dashboardsSource
Dashboards (each page is also an entity) in the account.
Deployments1
- Create deployment markerDestinationNot retried automaticallyApproval before production
Records a deployment on an entity (change tracking), for example from a CI/CD release.
Entities2
- Get entitySource
One entity by GUID with its tags and alert severity.
- Search entitiesSource
Applications, hosts, monitors, dashboards, workloads and other entities matching structured criteria.
Entity tags1
- Add entity tagsDestinationProvider duplicate protectionApproval before production
Adds tag values to an entity. Existing tags are kept; repeating the call converges.
Incidents1
- List incidentsSourceIncremental
Alert incidents (condition violations) with their policy and condition.
Issues2
- List issuesSourceIncremental
Alert issues with priority, state, correlated entities and timing.
- Resolve issueDestinationProvider duplicate protectionApproval before production
Resolves (closes) an alert issue, for example when the linked ticket is closed.
Notification channels1
- List notification channelsSource
Channels that workflows use to notify a destination.
Notification destinations1
- List notification destinationsSource
Email, webhook, Slack and other destinations (credentials are never read).
Nrql1
- Run NRQL querySource
Runs a read-only NRQL query and returns each result row as a record.
Service level indicators1
- List service level indicatorsSource
SLIs and their objectives defined on one service entity.
Service levels1
- List service levelsSource
Service level indicator entities in the account.
Synthetic monitors2
- Get synthetic monitorSource
One synthetic monitor by entity GUID.
- List synthetic monitorsSource
Synthetic monitors in the account with their monitor type and alert severity.
User groups1
- List user groupsSource
Groups in an authentication domain.
Users1
- List usersSource
Users in an authentication domain with their user type, last activity and groups.
Workloads3
- Create workloadDestinationNot retried automaticallyApproval before production
Creates a workload from entity GUIDs and dynamic entity search queries.
- List workloadsSource
Workloads in the account, found through entity search.
- Update workloadDestinationProvider duplicate protectionApproval before production
Renames a workload or replaces its entities and search queries.
Access and limits
- Authentication
- User API key
- Plans and access
- All New Relic plans, including the free tier. User keys act with the user's role and account access; alert and workload changes need the matching capabilities.
- Test environment
- A free New Relic account works for testing.
- Rate limits
- NerdGraph limits concurrent requests per user (25) and query complexity; NRQL queries are also subject to per-account query limits. Throttling is reported as HTTP 429 or GraphQL errors.
- Pagination
- Opaque nextCursor values passed back as the cursor argument.
- Provider events
- Workflows deliver issue notifications to webhook destinations. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Dashboard, workload, synthetic monitor and service level lists use NerdGraph entity search with a query built from validated values (account, name contains, one tag); values containing quotes are rejected.
- Synthetic monitor reads return the documented entity fields (type, tags, alert severity, reporting). Monitor scripts, steps and secure credentials are not read.
- Service level indicators are read per service entity (entity.serviceLevel.indicators), as documented; SLI attainment values come from NRQL.
- NRQL queries and the change-event list consume query capacity: on New Relic's compute (CCU) pricing every query, and API call, consumes Compute Capacity Units, so these reads are marked billable and are not retried automatically.
- NRQL queries take an optional timeout of 5 to 120 seconds; the change-event list is limited to a 90-day window and 100 rows per call.
- Deployment markers use changeTrackingCreateDeployment (legacy, still supported); generic change events use changeTrackingCreateEvent. Timestamps must be within 24 hours of now. customAttributes are sent as a GraphQL object literal as documented; nested values are not accepted.
- Users and groups are read per authentication domain through organization user management and require organization-level user management access. Group lists are a single page.
- Workflow, destination and channel fields beyond id and name follow the NerdGraph schema used by New Relic's official Go client; destination credentials and properties are never read.
- Not implemented: dashboard, monitor, service level, workflow, destination and channel writes; NRQL condition create; deletes of any kind (intentional exclusions).
- Entity search uses NerdGraph's structured query builder (name, domain, type, alert severity, reporting, tags); free-text entity queries are not accepted.
- Workload lists use entity search with type WORKLOAD because the workload collection read is deprecated.
- Issue and incident filters and time windows are sent as validated GraphQL literals; the argument shapes follow New Relic's issues tutorial.
- NRQL queries must start with SELECT, FROM or SHOW and are limited to 4,000 characters; each NRQL result row is returned as one record.
- Policy, workload, deployment and change-event creates have no idempotency key; uncertain writes are not repeated automatically.
Developer reference
- Create the New Relic credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose New Relic, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/new-relic and the Connections API.