When a scan of a site finds a blocker, ValiqAI opens an Opsgenie alert (priority P1) with the worst problem in the message and the run in its details, so the on-call schedule you already have hears about it.
Every alert for a site shares one alias, so more failing scans add to the same alert instead of opening new ones, and the first clean scan closes it.
Atlassian stopped selling Opsgenie in June 2025 and ends support in April 2027. It works today; if your team is moving to Jira Service Management or another tool, tell us which.
How it works
- A scan finds a blocker. Or a high problem too (priority P2), if you turn that on.
- Opsgenie alerts on-call. One alert per site, tagged valiqai, with the site as the entity and a link to the evidence.
- It closes itself. When a later scan of the site is clean, ValiqAI closes the alert by its alias.
Set up
In ValiqAI, open Integrations › Opsgenie in your workspace.
- In Opsgenie, open Settings › Integrations and add an API integration for the team that should be alerted.
- Paste its API key here, pick US or EU, and send a test.
- Choose whether high problems alert too, and whether clean scans close the alert.
Plan
Opsgenie is on the Teams plan (Teams and Enterprise). A connection made before a plan change keeps working.
With AI tools
With the ValiqAI MCP server added to your AI coding tool, you can ask:
- “Scan production with ValiqAI now; a blocker alerts on-call in Opsgenie.”
- “Is the ValiqAI alert for staging still open? What did the last scan find?”