Skip to main content
Opsgenie in Novu is routed per subscriber. Each subscriber brings their own Opsgenie API integration key (GenieKey), so one workflow trigger can raise alerts in different Opsgenie accounts and teams for different recipients. The integration itself never stores an API key. It acts as the anchor that per-subscriber channel endpoints hang off of.
There is no shared, environment-level Opsgenie API key. If a subscriber has no Opsgenie endpoint registered, the Tool step is marked skipped for that subscriber; no alert is created and no error is raised.

Prerequisites

Get an API key from Opsgenie

Every subscriber routes to their own Opsgenie account or team, so each subscriber needs an API key from their API integration.
1

Open integrations in Opsgenie

In Opsgenie, go to SettingsIntegrations. To scope alerts to a single team, open the team and go to its Integrations tab instead.
2

Add an API integration

Click Add integration, choose API, and save. Opsgenie creates an API integration with alert create permissions.
3

Copy the API key

Opsgenie generates a UUID-format API Key (for example xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Copy it. This is the GenieKey Novu will store for the subscriber.
Use a key from an API integration (Settings → Integrations, or a team’s integrations). Keys from the account-level API Key Management page will not work: the Opsgenie Alert API rejects them with an authentication error.
The API key grants the ability to create alerts in the Opsgenie account. Treat it like a password: keep it on your server, never embed it in client-side code, and never log it.

Add Opsgenie in Novu

1

Open the Integrations Store

In the Novu dashboard, click Integrations Store in the sidebar.
2

Add Opsgenie

Click Connect Provider, select Tool, then choose Opsgenie.
3

Create the integration

Opsgenie has no environment-level credentials, so there is nothing to paste on this screen. Click Create Integration to save it. This gives you the integrationIdentifier you’ll reference below when registering subscribers’ API keys.

Store a subscriber’s API key

Register each subscriber’s API key as a channel endpoint on the Opsgenie integration. Novu encrypts the API key at rest on the linked channel connection and hydrates the wire shape { apiKey, region } back on reads.
Registering an endpoint requires your Novu secret key. Always call the channel-endpoints API from your server, never from a browser or mobile client. A typical flow is: your app UI sends the API key to your backend, and your backend forwards it to Novu.

Create the endpoint

Send the API key as an opsgenie_integration endpoint. Set createSubscriberIfMissing: true so this call also provisions the Novu subscriber the first time an end user connects Opsgenie, with no separate identify call required.

Endpoint shape

One endpoint per subscriber, per integration

A subscriber may have at most one Opsgenie endpoint per integration. A second POST with the same (subscriberId, integrationIdentifier) returns 409 Conflict. Rotate the API key by PATCHing the existing endpoint instead:

Reading and disconnecting

Reads return the full wire shape (including the API key), so you can display connection status. Mask it in your UI (the Novu dashboard shows only the last four characters).
Delete the endpoint to disconnect a subscriber. Novu cascades the delete to the underlying channel connection, dropping the encrypted API key:

Page a subscriber from a workflow

Once a subscriber has an Opsgenie endpoint, add a Tool step with Opsgenie to your workflow and trigger it like any other workflow.
1

Add a Tool step

In the workflow editor, add a step and select Tool as the channel. Choose the Opsgenie integration you created.
2

Write the alert message

The step content becomes the alert message in the Opsgenie Alert API request. Use dynamic placeholders such as {{payload.orderNumber}} or {{subscriber.firstName}}. Opsgenie caps message at 130 characters; Novu truncates longer content.
3

Trigger the workflow

Send a trigger for a subscriber who has connected Opsgenie. Novu resolves that subscriber’s API key and creates an alert in their Opsgenie account. Opsgenie accepts the request asynchronously (202 with a requestId).

Alert payload defaults and overrides

The deterministic alias is Opsgenie’s deduplication key: Novu retries for the same step will deduplicate into the same Opsgenie alert instead of creating duplicates.

What happens without an endpoint

If a workflow triggers for a subscriber who has no Opsgenie endpoint on the target integration, Novu marks the step as skipped in the Activity feed for that subscriber and does not create an alert. Other subscribers on the same trigger are unaffected. Each is routed to their own Opsgenie account.

Create a channel endpoint

API reference for POST /v1/channel-endpoints, including the opsgenie_integration variant.

Rotate an API key

API reference for PATCH /v1/channel-endpoints/:identifier. Use this to rotate an existing subscriber’s API key.