PagerDuty integration
Page the right person when your infrastructure breaks, and hear back when they act
InfraNest watches your websites, APIs, servers, domains and certificates. Connect PagerDuty and a monitor going down pages your on-call team, a recovery resolves the incident by itself, and an acknowledgement in either tool shows up in the other.
On Pro and up · 14-day Pro trial, no credit card · Your schedules stay untouched
- Outages page on-call, recoveries resolve the incident
- Acknowledge or resolve in either tool, the other follows
- Page for expiring certificates and domains, not just downtime
- Set up in one click, without touching your escalation policies
- StorefrontDefaultMonitor alerts page this serviceRemove
- Platform on-callUsed by automations only — monitor alerts don’t page itSend monitor alerts hereRemove
Last test 3 minutes ago · PagerDuty accepted it · PagerDuty reported back
Send test incidentCheck setupA monitor goes down, on-call is paged, and the incident ends when it recovers
When a monitor goes down, InfraNest sends a trigger to the PagerDuty service you chose, at critical severity for an outage and warning for a degradation. Repeated alerts for the same outage share one grouping key, so they land as one PagerDuty incident rather than a page every minute. When the monitor recovers, InfraNest resolves that same incident, so nobody closes it by hand at three in the morning. Checks run from several regions and only change status when enough of them agree, so a single flaky probe does not wake anyone up.
- Outages page at critical, degradations at warning
- One PagerDuty incident per outage, however many alerts it raises
- Resolved in PagerDuty the moment the monitor recovers
- Send warnings to Slack and only hard-down to PagerDuty — see alert routing
Or let an automation act on it
Acknowledge or resolve in either tool, and the other follows
Responders work in PagerDuty, and the rest of the team looks at InfraNest. Both should say the same thing. When someone acknowledges or resolves the incident in InfraNest, PagerDuty follows. When a responder acknowledges or resolves it in PagerDuty, a signed webhook tells InfraNest, and the InfraNest incident updates to match. After you connect, one test incident checks the whole round trip and reports each direction on its own evidence.
- Acknowledgements and resolutions sync both ways
- Updates from PagerDuty arrive through a signed webhook
- A test incident proves both directions, then resolves itself
- Page several PagerDuty services from one account
Acknowledging in InfraNest first works the same way, in the other direction.
Page for what a monitor never sees
An expiring certificate takes a site down just as surely as a crashed server, but no uptime check fires until it already has. With InfraNest automations, a certificate about to expire, a domain about to lapse or a DNS zone that changed at the provider can page on-call through PagerDuty, and a later step can acknowledge or resolve the same incident. It works the other way too: when a PagerDuty incident is triggered, acknowledged, resolved, escalated or reopened, a rule can open a maintenance window or post on your status page.
- Trigger, acknowledge and resolve PagerDuty incidents from any rule
- PagerDuty incident events as triggers for your own rules
- Choose the service and severity per rule
- Nothing runs until you switch the rule on — see how rules are built
Built from the automation catalogue: any trigger, any action.
Connected in one click, and your schedules stay yours
Sign in to PagerDuty, approve access, and pick the service to page. Before anything is created, InfraNest lists exactly what it will set up: its own Events API v2 integration on that service, an alert destination for monitor alerts, and a webhook for updates coming back. It leaves escalation policies, schedules and the integrations you already have alone, and on disconnect it removes only what it created. Prefer not to use OAuth? Paste a service integration key instead.
- No integration key to copy when you connect in one click
- A preview of every change before it is made
- Escalation policies, schedules and existing integrations untouched
- Pause at any time without losing the setup
Choose where InfraNest should page. We will configure the selected outcomes together after one confirmation.
InfraNest will
- • Create or reuse an InfraNest-owned Events API v2 integration on the selected service.
- • Use the authorized account to list services and manage only the resources InfraNest records as its own.
- • Create an alert destination for outbound monitor notifications.
- • Create an account webhook for acknowledgements, resolutions and automation triggers.
- • Leave escalation policies, schedules and existing PagerDuty integrations untouched.
Connect PagerDuty to your own monitors
On Pro and up, with a 14-day trial and no credit card. Connect in one click and send a test incident to see the round trip.
Connect PagerDuty in about two minutes
Connect with one click and pick the service to page, or paste a service integration key if you prefer. You need the Owner or Admin role in InfraNest, and a PagerDuty user who can add integrations to the service.
- 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.
Often connected together
Questions about the PagerDuty integration
#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.
Let on-call hear about it first, and let InfraNest hear back
Create your account (it starts with 14 days of Pro), connect PagerDuty in one click, and send a test incident. Your schedules and escalation policies stay exactly as they are.
Free plan · No credit card required · Set up in minutes