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
- An Opsgenie account with permission to manage integrations
- Access to the Novu dashboard
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 Settings → Integrations. 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.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.
Create the endpoint
Send the API key as anopsgenie_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.
- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
Endpoint shape
One endpoint per subscriber, per integration
A subscriber may have at most one Opsgenie endpoint per integration. A secondPOST 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).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).- Node.js
- Python
- Go
- PHP
- .NET
- Java
- cURL
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.Related
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.