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 can resolve the incident for you, 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 can resolve the incident
- Acknowledge or resolve in either tool, the other follows
- Page on-call yourself, from a critical problem or an incident
- Page for expiring certificates and domains, not just downtime
One incident, not several: the effects are grouped under the cause.
- 2:33 PMDeploy of northwyndr/storefront (f19e6c7)Deploys
- 2:36 PMCheckout flow failed: Checkout returning 503Monitoring
- 2:36 PMAPI health failed too, grouped under this incidentMonitoring
- 2:36 PMAlert sent to Ops team — email, On-call — critical only, #infra-alerts, Engineering — Discord, Northwind on-call — PagerDutyNotifications
- status.payrail.examplePayment gateway status: degraded API in eu-westlinked · not kept in steplinked 33 minutes ago
- Q3NWCHK7Y1Paged on-callPagedpaged 40 minutes ago
A monitor goes down, on-call is paged, and recovery can end the incident
When a monitor goes down, InfraNest pages the PagerDuty service you chose, at critical severity for an outage and warning for a degradation. Repeated alerts for the same outage update one PagerDuty incident rather than paging every minute. When the monitor recovers, InfraNest resolves that same incident, unless you set the service to leave that to a person. On Business, 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 when the monitor recovers, on by default
- 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, 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
- Notes copy both ways, never to your status page
- 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 on-call yourself, for a problem that does not page on its own
Not every problem pages automatically. A domain that expires in six days with a failed renewal, or a checkout that fails for a few percent of visitors, may be below what pages by itself and still need someone now. Open the problem’s menu and choose Page on-call. The confirmation names the PagerDuty service it goes to, the urgency and, when PagerDuty can tell, who is on call, and nothing is sent until you confirm. The page then shows on the problem and on the incident, and InfraNest resolves it when the problem clears or the incident is resolved, unless the service is set to be resolved by a person.
- On critical problems on Home, and on incidents not yet paged
- See where it goes, and pick another service if it belongs to another team
- Shown on the card and the incident, so nobody pages twice
- Each page in the audit log, with the name of who sent it
This pages Priya Raghunathan, on call for Platform — production in PagerDuty, right now, at high urgency.
The certificate for vpn.northwind.example will not renew itself
Open in InfraNest
Resolved in PagerDuty by itself once this clears.
- Q2MKTBLP4NPaged on-callResolvedpaged 6 days ago
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 on that service and in your account. It leaves escalation policies, schedules and the integrations you already have alone, and on disconnect it removes only what it created. Prefer to set it up yourself? That works too.
- Nothing to copy between the two tools 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
Connect your PagerDuty account
Get one-click sign-in so acknowledgements and notes sync both ways; select Connect PagerDuty on the PagerDuty page under Integrations.
- 2
Choose the service to page
Pick which PagerDuty service receives your incidents, then review what InfraNest will set up and select Finish setup.
- 3
Send a test incident
Confirm PagerDuty accepts and reports back by selecting Send test incident on the account.
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: Sign in with PagerDuty, or an integration key. 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 happens if I revoke access or the integration key stops working?
Paging stops working until it's fixed, and InfraNest shows the account as no longer accepted or failing so you notice. Nothing already set up in PagerDuty is removed — select Connect again and sign in, or update the key, to pick back up.
#Does InfraNest change anything else in my PagerDuty account?
It only creates an Events API v2 integration named InfraNest on each service you choose, one webhook for the account, and maintenance windows on services where you turn that on. It never touches your escalation policies, schedules, users, teams or other integrations, and only ever removes what it created.
#Does every page open a new incident?
No — repeat alerts for the same problem update the existing incident, and several monitors failing together on one server share a single incident, so on-call is paged once per outage rather than once per alert.
#Can I resolve PagerDuty incidents by hand instead of automatically?
Yes, resolving automatically when the problem ends is a per-service setting you can turn off, which leaves the incident for a person to resolve in PagerDuty.
#What do I need before connecting PagerDuty?
You'll need a PagerDuty Admin or Account Owner to install InfraNest once for one-click connect (or an Integration Key from a service's Events API v2 integration to set it up yourself) — see the setup guide.
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