New Relic Issue actions

This page provides a reference for all New Relic Issue actions available in the workflow automation actions catalog. These actions let you acknowledge, unacknowledge, and resolve Alert Intelligence issues, and query issues to enable conditional logic in your workflows.

Prerequisites

Before using New Relic Issue actions in workflow automation, ensure you have:

A New Relic account with appropriate permissions to manage Alert Intelligence issues.
The necessary permissions for the specific New Relic services you plan to use.

Issue actions

Acknowledges an open New Relic issue (AI Issues), marking it as ACKNOWLEDGED. New Relic records who acknowledged it and the timestamp on the issue record (acknowledgedBy / acknowledgedAt) as a side effect of the mutation. Built on newrelic.nerdgraph.execute.

The following table describes all available input fields for this action.

Input	Optionality	Type	Description	Example
accountId	Required	Int	The New Relic account that owns the issue. Must be a positive integer.	`123456`
issueId	Required	String	The AI Issues issue identifier to acknowledge. Must be a valid UUID.	`"123e4567-e89b-12d3-a456-426614174000"`
selectors	Optional	List	JQ selectors to extract specific values from the response.	`selectors: - name: action expression: ".data.aiIssuesAckIssue.result.action"`

The following table describes all output fields returned by this action.

Output	Type	Description
success	Boolean	`true` when the step executed without an HTTP/transport error, independent of the mutation's own error field (`data.aiIssuesAckIssue.error`).
errorMessage	String	Contains an error message only when the call fails at the HTTP/transport level, distinct from `data.aiIssuesAckIssue.error` (the mutation's own business-logic error field). `null` on success.
data	Map	NerdGraph response: `{ "data": { "aiIssuesAckIssue": { "error": null, "result": { "accountId": 123456, "action": "ACK", "issueId": "123e4567-e89b-12d3-a456-426614174000" } } } }` Use `selectors` to extract `error`, `action`, `issueId`, or `accountId` from `data`.

Output

Type

Description

success

Boolean

true when the step executed without an HTTP/transport error, independent of the mutation's own error field (data.aiIssuesAckIssue.error).

errorMessage

String

Contains an error message only when the call fails at the HTTP/transport level, distinct from data.aiIssuesAckIssue.error (the mutation's own business-logic error field). null on success.

data

Map

NerdGraph response:

{
  "data": {
    "aiIssuesAckIssue": {
      "error": null,
      "result": {
        "accountId": 123456,
        "action": "ACK",
        "issueId": "123e4567-e89b-12d3-a456-426614174000"
      }
    }
  }
}

Use selectors to extract error, action, issueId, or accountId from data.

The following example shows how to use this action.

Workflow example
`name: newrelic_issue_acknowledge_workflow description: acknowledge a newrelic issue steps: - name: newrelic_issue_acknowledge type: action action: newrelic.issue.acknowledge version: 1 inputs: accountId: 123456 issueId: "123e4567-e89b-12d3-a456-426614174000" next: end`

Workflow example

name: newrelic_issue_acknowledge_workflow
description: acknowledge a newrelic issue
steps:
  - name: newrelic_issue_acknowledge
    type: action
    action: newrelic.issue.acknowledge
    version: 1
    inputs:
      accountId: 123456
      issueId: "123e4567-e89b-12d3-a456-426614174000"
    next: end

Reverts a previously acknowledged New Relic issue (AI Issues) back to an unacknowledged state, clearing the acknowledgedBy / acknowledgedAt fields on the issue record. Built on newrelic.nerdgraph.execute.

The following table describes all available input fields for this action.

Input	Optionality	Type	Description	Example
accountId	Required	Int	The New Relic account that owns the issue. Must be a positive integer.	`123456`
issueId	Required	String	The AI Issues issue identifier to revert to unacknowledged. Must be a valid UUID.	`"123e4567-e89b-12d3-a456-426614174000"`
selectors	Optional	List	JQ selectors to extract specific values from the response.	`selectors: - name: action expression: ".data.aiIssuesUnackIssue.result.action"`

The following table describes all output fields returned by this action.

Output	Type	Description
success	Boolean	`true` when the step executed without an HTTP/transport error, independent of the mutation's own error field (`data.aiIssuesUnackIssue.error`).
errorMessage	String	Contains an error message only when the call fails at the HTTP/transport level, distinct from `data.aiIssuesUnackIssue.error` (the mutation's own business-logic error field). `null` on success.
data	Map	NerdGraph response: `{ "data": { "aiIssuesUnackIssue": { "error": null, "result": { "accountId": 123456, "action": "UNACK", "issueId": "123e4567-e89b-12d3-a456-426614174000" } } } }` Use `selectors` to extract `error`, `action`, `issueId`, or `accountId` from `data`.

Output

Type

Description

success

Boolean

true when the step executed without an HTTP/transport error, independent of the mutation's own error field (data.aiIssuesUnackIssue.error).

errorMessage

String

Contains an error message only when the call fails at the HTTP/transport level, distinct from data.aiIssuesUnackIssue.error (the mutation's own business-logic error field). null on success.

data

Map

NerdGraph response:

{
  "data": {
    "aiIssuesUnackIssue": {
      "error": null,
      "result": {
        "accountId": 123456,
        "action": "UNACK",
        "issueId": "123e4567-e89b-12d3-a456-426614174000"
      }
    }
  }
}

Use selectors to extract error, action, issueId, or accountId from data.

The following example shows how to use this action.

Workflow example
`name: newrelic_issue_unacknowledge_workflow description: revert an acknowledged newrelic issue steps: - name: newrelic_issue_unacknowledge type: action action: newrelic.issue.unacknowledge version: 1 inputs: accountId: 123456 issueId: "123e4567-e89b-12d3-a456-426614174000" next: end`

Workflow example

name: newrelic_issue_unacknowledge_workflow
description: revert an acknowledged newrelic issue
steps:
  - name: newrelic_issue_unacknowledge
    type: action
    action: newrelic.issue.unacknowledge
    version: 1
    inputs:
      accountId: 123456
      issueId: "123e4567-e89b-12d3-a456-426614174000"
    next: end

Resolves an open New Relic issue (AI Issues), closing it once remediation steps are complete. The issue's state transitions to CLOSED and New Relic records the resolution on the issue record. Built on newrelic.nerdgraph.execute.

The following table describes all available input fields for this action.

Input	Optionality	Type	Description	Example
accountId	Required	Int	The New Relic account that owns the issue. Must be a positive integer.	`123456`
issueId	Required	String	The AI Issues issue identifier to resolve. Must be a valid UUID.	`"123e4567-e89b-12d3-a456-426614174000"`
selectors	Optional	List	JQ selectors to extract specific values from the response.	`selectors: - name: action expression: ".data.aiIssuesResolveIssue.result.action"`

The following table describes all output fields returned by this action.

Output	Type	Description
success	Boolean	`true` when the step executed without an HTTP/transport error, independent of the mutation's own error field (`data.aiIssuesResolveIssue.error`).
errorMessage	String	Contains an error message only when the call fails at the HTTP/transport level, distinct from `data.aiIssuesResolveIssue.error` (the mutation's own business-logic error field). `null` on success.
data	Map	NerdGraph response: `{ "data": { "aiIssuesResolveIssue": { "error": null, "result": { "accountId": 123456, "action": "RESOLVE", "issueId": "123e4567-e89b-12d3-a456-426614174000" } } } }` Use `selectors` to extract `error`, `action`, `issueId`, or `accountId` from `data`.

Output

Type

Description

success

Boolean

true when the step executed without an HTTP/transport error, independent of the mutation's own error field (data.aiIssuesResolveIssue.error).

errorMessage

String

Contains an error message only when the call fails at the HTTP/transport level, distinct from data.aiIssuesResolveIssue.error (the mutation's own business-logic error field). null on success.

data

Map

NerdGraph response:

{
  "data": {
    "aiIssuesResolveIssue": {
      "error": null,
      "result": {
        "accountId": 123456,
        "action": "RESOLVE",
        "issueId": "123e4567-e89b-12d3-a456-426614174000"
      }
    }
  }
}

Use selectors to extract error, action, issueId, or accountId from data.

The following example shows how to use this action.

Workflow example
`name: newrelic_issue_resolve_workflow description: resolve a newrelic issue steps: - name: newrelic_issue_resolve type: action action: newrelic.issue.resolve version: 1 inputs: accountId: 123456 issueId: "123e4567-e89b-12d3-a456-426614174000" next: end`

Workflow example

name: newrelic_issue_resolve_workflow
description: resolve a newrelic issue
steps:
  - name: newrelic_issue_resolve
    type: action
    action: newrelic.issue.resolve
    version: 1
    inputs:
      accountId: 123456
      issueId: "123e4567-e89b-12d3-a456-426614174000"
    next: end

Queries and lists New Relic issues (AI Issues) for an account, returning real-time status, timeline, correlated entities, and impact details for active or past issues. Supports filtering by state, priority, source, entity, condition, policy, correlation and acknowledgment status, a time window, and cursor-based pagination. Built on newrelic.nerdgraph.execute.

The following table describes all available input fields for this action.

Input	Optionality	Type	Description	Example
accountId	Required	Int	The New Relic account whose issues to list. Must be a positive integer.	`123456`
issueIds	Optional	List	Issue IDs to include. Must be a JSON array of UUID strings.	`["123e4567-e89b-12d3-a456-426614174000"]`
states	Optional	List	One or more of `ACTIVATED`, `CLOSED`, `CREATED`, `DEACTIVATED`.	`["ACTIVATED", "CREATED"]`
priority	Optional	List	One or more of `CRITICAL`, `HIGH`, `MEDIUM`, `LOW`.	`["CRITICAL", "HIGH"]`
sources	Optional	List	One or more of `newrelic` (raised by New Relic's alerting engine) or `rest` (created externally via the REST API).	`["newrelic"]`
entityGuids	Optional	List	Entity GUIDs to filter by.	`["MTIzNDU2..."]`
entityTypes	Optional	List	Entity types to filter by.	`["APPLICATION"]`
conditionIds	Optional	List	Alert condition IDs to filter by. Must be a JSON array of integers.	`[10001, 10002]`
policyIds	Optional	List	Alert policy IDs to filter by. Must be a JSON array of integers.	`[5001]`
isAcknowledged	Optional	Boolean	Acknowledgment status filter. `true` for acknowledged issues only. `false` for unacknowledged issues only.	`false`
isCorrelated	Optional	Boolean	Indicates whether New Relic's Applied Intelligence has merged this issue with other related issues to reduce noise.	`false`
mutingStates	Optional	List	Notification suppression status. One or more of `NOT_MUTED`, `FULLY_MUTED`, or `PARTIALLY_MUTED`.	`["NOT_MUTED"]`
contains	Optional	String	Case-sensitive, free-text match on key issue attributes.	`"checkout-service"`
startTime	Optional	Int	Time window start, epoch milliseconds. Must be non-negative. Requires `endTime` — both fields must be present for the time window filter to apply.	`1785900000000`
endTime	Optional	Int	Time window end, epoch milliseconds. Must be non-negative. Requires `startTime` — both fields must be present for the time window filter to apply.	`1785998400000`
cursor	Optional	String	Opaque pagination token from a prior call's `nextCursor` output. Retrieves the next page of results.	`"eyJpZCI6IjE..."`
selectors	Optional	List	JQ selectors to extract specific values from the response.	`selectors: - name: issues expression: ".data.actor.account.aiIssues.issues.issues" - name: nextCursor expression: ".data.actor.account.aiIssues.issues.nextCursor"`

The following table describes all output fields returned by this action.

Output	Type	Description
success	Boolean	`true` when the step executed without an HTTP/transport error.
errorMessage	String	Contains an error message only when the call fails at the HTTP/transport level. `null` on success.
data	Map	NerdGraph response. Contains `data.actor.account.aiIssues.issues.issues` (array of issue objects) and `data.actor.account.aiIssues.issues.nextCursor` (`null` when no further pages exist). The following is a representative subset of the response — each issue carries the full `AiIssuesIssue` field set: `issueId`, `title`, `description`, `priority`, `state`, `createdAt`, `updatedAt`, `closedAt`, `activatedAt`, `acknowledgedAt/By/ByChannel`, `closedBy/ByChannel`, `investigatedAt/By/ByChannel`, `unAcknowledgedAt/By/ByChannel`, `sources`, `origins`, `entityGuids/Names/Types`, `conditionName/FamilyId/Product`, `policyIds/Name`, `correlationRuleIds/Names/Descriptions`, `correlationStatus`, `correlatedBy`, `isCorrelated`, `isIdle`, `mutingState`, `totalIncidents`, `incidentIds`, `deepLinkUrl`, `accountIds`, `parentMergeId`, `mergeReason`, `eventType`, `wildcard`, `dataMlModules` (list of key/value pairs), and `realIssueCount`. Use `selectors` to extract specific values. `{ "data": { "actor": { "account": { "aiIssues": { "issues": { "issues": [ { "issueId": "123e4567-e89b-12d3-a456-426614174000", "title": ["Example issue title"], "state": "ACTIVATED", "priority": "CRITICAL", "entityNames": ["example-entity"] } ], "nextCursor": null } } } } } }`

The following examples show how to use this action with different filter configurations.

Workflow example
No filters — list every issue on the account, regardless of state, priority, or other filters. Only `accountId` is required: `name: newrelic_issue_list_all description: list all issues for an account with no filters steps: - name: newrelic_issue_list type: action action: newrelic.issue.list version: 1 inputs: accountId: 123456 next: end` The following example uses basic filters to list active, high-priority issues for an account: `name: newrelic_issue_list_workflow description: list newrelic issues steps: - name: newrelic_issue_list type: action action: newrelic.issue.list version: 1 inputs: accountId: 123456 states: ["ACTIVATED", "CREATED"] priority: ["CRITICAL", "HIGH"] next: end` The following example uses multiple filters for unacknowledged, unmuted, critical issues within a specific time window, with selectors flattening the response for pagination: name: newrelic_issue_list_advanced description: list unacknowledged critical issues in a time window steps: - name: newrelic_issue_list type: action action: newrelic.issue.list version: 1 inputs: accountId: 123456 states: ["ACTIVATED"] priority: ["CRITICAL"] isAcknowledged: false mutingStates: ["NOT_MUTED"] startTime: 1785900000000 endTime: 1785998400000 selectors: - name: issues expression: ".data.actor.account.aiIssues.issues.issues" - name: nextCursor expression: ".data.actor.account.aiIssues.issues.nextCursor" next: end To page through additional results from example 3, take the `nextCursor` output and pass it back in as the `cursor` input on a follow-up call.

Workflow example

No filters — list every issue on the account, regardless of state, priority, or other filters. Only accountId is required:

name: newrelic_issue_list_all
description: list all issues for an account with no filters
steps:
  - name: newrelic_issue_list
    type: action
    action: newrelic.issue.list
    version: 1
    inputs:
      accountId: 123456
    next: end

The following example uses basic filters to list active, high-priority issues for an account:

name: newrelic_issue_list_workflow
description: list newrelic issues
steps:
  - name: newrelic_issue_list
    type: action
    action: newrelic.issue.list
    version: 1
    inputs:
      accountId: 123456
      states: ["ACTIVATED", "CREATED"]
      priority: ["CRITICAL", "HIGH"]
    next: end

The following example uses multiple filters for unacknowledged, unmuted, critical issues within a specific time window, with selectors flattening the response for pagination:

name: newrelic_issue_list_advanced
description: list unacknowledged critical issues in a time window
steps:
  - name: newrelic_issue_list
    type: action
    action: newrelic.issue.list
    version: 1
    inputs:
      accountId: 123456
      states: ["ACTIVATED"]
      priority: ["CRITICAL"]
      isAcknowledged: false
      mutingStates: ["NOT_MUTED"]
      startTime: 1785900000000
      endTime: 1785998400000
      selectors:
        - name: issues
          expression: ".data.actor.account.aiIssues.issues.issues"
        - name: nextCursor
          expression: ".data.actor.account.aiIssues.issues.nextCursor"
    next: end

To page through additional results from example 3, take the nextCursor output and pass it back in as the cursor input on a follow-up call.

Prerequisites

Issue actions

Acknowledge issue

Unacknowledge issue

Resolve issue

List issues

New Relic Issue actions

Prerequisites.css-21sua1{background:none;border:none;width:0;padding:0;}

Issue actions

Unacknowledge issue

Resolve issue

List issues

Prerequisites