Page your on-call team the moment a monitor goes down
Turn monitor failures into PagerDuty incidents, and keep both sides in sync automatically
Connect a PagerDuty service so monitor problems reach your on-call team without anyone manually opening an incident.
- Automatic paging on failure: a monitor going down triggers a PagerDuty incident on the service you choose, and recovery resolves it for you.
- Two-way status: acknowledging or resolving in InfraNest updates the linked PagerDuty incident, and doing it in PagerDuty updates InfraNest back — no more checking both tools to know what's actually still open.
- Automation triggers and actions: trigger, acknowledge, or resolve PagerDuty incidents from automations, so events a monitor never sees — an expiring certificate, a failed job — can still page someone.
- One destination per service: add more destinations if you need to page different services or teams.
NoteTwo-way sync (PagerDuty → InfraNest) needs a short one-time setup on the destination; paging and outbound updates work as soon as you add the key.
What it looks like in InfraNest
Or let an automation act on it
What you can do
Once PagerDuty is connected, this is what InfraNest can do with it.
- Automatic incident open/resolve on monitor status
- Two-way acknowledge and resolve sync
- Automation-triggered paging
- Per-service destinations
How to connect it
- 1
Add an Events API v2 integration in PagerDuty
In PagerDuty, open Services → your service → Integrations → Add integration, and add Events API v2. Copy the 32-character Integration Key it shows.
- 2
Add a PagerDuty destination in InfraNest
Go to Alerts → Destinations, choose Add a destination, and select PagerDuty.
- 3
Paste the Integration Key and test
Paste the key, select Test to fire a test page, and confirm an incident appears in PagerDuty. Save once it works.
- 4
Route alerts to the destination
Choose PagerDuty when deciding which alerts go where, so monitor failures page that service.
That’s it — PagerDuty is connected.
Full setup guideSet up with AI
I use PagerDuty, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Integration key, or connect in one click. Walk me through creating that in PagerDuty: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
Questions
#What key does PagerDuty need, exactly?
You need the Events API v2 Integration Key from a specific service's Integrations tab, not a REST API Access Key. Pasting the REST key will fail with an invalid-key error when you test the connection.
#What happens if the Integration Key is revoked or deleted?
Paging to that service will stop working, and testing the destination will fail. Add a new Events API v2 integration on the service, generate a fresh key, and update the destination in InfraNest with it.
#Does InfraNest change anything in my PagerDuty account?
InfraNest adds an Events API v2 integration's worth of activity to the service you connect — it creates, acknowledges, and resolves incidents through that key. It doesn't touch your other PagerDuty services or configuration.
#Can I page different teams for different alerts?
Yes — each destination pages one PagerDuty service, so add a separate destination for each service or team you want to route alerts to.
#Why didn't a repeated alert create a new incident?
PagerDuty groups repeated alerts for the same unresolved issue into the existing open incident rather than starting a new one. Once that incident is resolved, the next occurrence will page fresh.
Often connected together
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes