> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# New Relic Webhook Setup Guide

> Configure New Relic to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/newrelic#getting-started) on the New Relic connector page.

<section data-guide-section data-guide-scopes="">
  <h2>How webhooks are set up</h2>

  <p>StackOne creates and manages the webhook subscription automatically when the account is connected, and removes it when the account is disconnected. There is nothing to configure in New Relic and no URL to paste.</p>

  <Steps>
    <Step title="Review what StackOne creates in New Relic">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>On connection, StackOne adds three items to the New Relic account named on the connection. You can see them in New Relic under <strong>Alerts</strong>, but do not edit or delete them while the connection is active.</p>

        <ul>
          <li>A webhook destination named <strong>StackOne Events</strong> that points at StackOne.</li>
          <li>A webhook channel that sends each alert issue update as JSON.</li>
          <li>A workflow named <strong>StackOne Events</strong> that forwards every alert issue in the account on all notification triggers.</li>
        </ul>
      </div>
    </Step>

    <Step title="Enable the events you need">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Enable the New Relic events you want in StackOne. The workflow already covers every notification trigger, and StackOne dispatches only the events you have enabled.</p>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>The events below can be enabled for this connection. They follow the lifecycle of New Relic alert issues. Only events selected in StackOne are delivered, and each one carries the issue id in `issueId` and the underlying change in `triggerEvent`.</p>

  <Steps>
    <Step title="Review alert issue events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to alert issues opened by New Relic alert policies and conditions.</p>

        <ul>
          <li><strong>Issue Activated</strong> (`issue.activated`) — Fired when an alert issue opens.</li>
          <li><strong>Issue Acknowledged</strong> (`issue.acknowledged`) — Fired when a user acknowledges an alert issue.</li>
          <li><strong>Issue Priority Changed</strong> (`issue.priority_changed`) — Fired when an alert issue's priority changes, for example when a critical incident joins it.</li>
          <li><strong>Issue Closed</strong> (`issue.closed`) — Fired when an alert issue closes, either because its incidents resolved or because a user closed it.</li>
          <li><strong>Issue Updated</strong> (`issue.updated`) — Fired for any other issue update, such as a new incident being added or the issue being marked as investigating.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Delivery format</h2>

  <p>Details of how New Relic delivers events to StackOne.</p>

  <Steps>
    <Step title="Review the delivery format">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>New Relic sends one request per alert issue notification, and each request describes a single issue. One change can fire more than one notification. When a critical incident joins an open issue, for example, New Relic sends a priority-changed notification and an incident-added update about a second apart. New Relic Test notifications carry fixed sample data, and StackOne acknowledges them without dispatching an event.</p>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.