On-call

PagerDuty

Page whoever is on call when a scan finds a blocker

Teams plan

When a scan of a site finds a blocker, ValiqAI opens a PagerDuty incident on the service you choose, so the person on call hears about a broken sign-up or checkout before customers do.

More failing scans of the same site update that incident instead of paging again, and the first clean scan resolves it.

Connecting PagerDuty in ValiqAI, then what PagerDuty shows after a scan, and back to the results.

How it works

  1. A scan finds a blocker. Or a high problem too, if you turn that on.
  2. PagerDuty pages on-call. One incident per site, with the worst problem in the title and a link to the evidence.
  3. It resolves itself. When a later scan of the site is clean, ValiqAI resolves the incident.

Set up

In ValiqAI, open Integrations › PagerDuty in your workspace.

  1. In PagerDuty, add an Events API v2 integration to the service that should be paged.
  2. Paste its integration key here and send a test.
  3. Choose whether high problems page too, and whether clean scans resolve.

Plan

PagerDuty 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; if it finds a blocker, on-call gets paged.”
  • “Is the ValiqAI incident for staging still open? What was the last scan result?”