> For the complete documentation index, see [llms.txt](https://archivedocs.stackstate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archivedocs.stackstate.com/monitors-and-alerts/notifications/channels/opsgenie.md).
# Opsgenie
## Configure Opsgenie notifications
To send notifications to Slack follow these steps:
1. [Create an integration in OpsGenie](#create-integration)
2. [Create the channel](#create-and-test-the-channel)
### Create integration
In order to integrate StackState with OpsGenie, a global "API key" needs to be created. The responders for a notification can be different for each notification and will be configured in StackState.
In Opsgenie, go to "Settings -> Integrations".
* Click the "Add integration" button
* Search for the "API" integration type.
* Choose a name for this integration, but *do not select an Assignee team*.
When the integration has been created, it will have an "API key".
### Create and test the channel
Select the appropriate region for your OpsGenie account and enter the "API key". Choose responders for the notification; *users*, *teams*, *schedules* and *escalations* are available for this.
Click the "Add channel" button. This adds the channel to the list of channels on the right. It will show a "Test" button. Pressing it will generate a test alert in OpsGenie.
## OpsGenie alerts for notifications
When a notification is opened a new OpsGenie alert is created. This message will be updated for changes, usually only when the health state changes. When the notification is closed the OpsGenie alert is closed again. A note on the alert contains the reason for closing it.
An OpsGenie alert generated by StackState
## Related
* [Troubleshooting](/monitors-and-alerts/notifications/troubleshooting.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://archivedocs.stackstate.com/monitors-and-alerts/notifications/channels/opsgenie.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.