IT Operations · Integration
PagerDuty
Add PagerDuty to your product for your customers, and give your AI agents governed access to it.
PagerDuty decides who gets woken up, so an embedded PagerDuty integration is how a condition your product detects becomes a page to whoever is genuinely on call. You can trigger, acknowledge and resolve incidents through the Events API, add notes and priorities, read services and the escalation policies behind them, and look up who is on call for a schedule right now. The care goes into noise: events carry a deduplication key, so a flapping check updates one incident instead of opening fifty, and routing follows the customer's own service and escalation setup rather than anything you can hard-code. fastn keeps each account's credentials and routing configuration per tenant and maintains the API surface.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer authorise their own PagerDuty account, so your product pages their on-call rota instead of emailing an inbox.
Trigger an incident against the service the customer chose, with a deduplication key so repeat signals update it.
Resolve automatically once the condition clears, leaving the timeline behind for the review afterwards.
Show who is currently on call inside your product, read from that customer's own schedules.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which incidents paged overnight, who acknowledged them and what is still open.
An agent adds a note or acknowledges an incident within the permissions granted, with the action attributed.
An agent checks the escalation policy on a service before it says who gets contacted next.
Example prompt
Who is on call for this service right now, and which incidents did it page for last night?
Set up PagerDuty in 4 steps
- 01Enable the PagerDuty connector from your fastn dashboard.
- 02Have each customer authorise their own PagerDuty account, so calls run under their credentials rather than a shared key.
- 03Decide which incidents, alerts and on-call schedules your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the PagerDuty integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PagerDuty integration without building it. Your customers connect their own PagerDuty account inside your product and work their incidents, alerts and on-call schedules there, with no per-customer code on your side.
- Handle the part that actually costs time: alerting is latency-critical and noisy, so filtering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a PagerDuty update is not your on-call problem.
- One integration serves your product and your agents. The same governed PagerDuty connection powers in-product features and gives AI agents scoped, audited access, so you route operational signal to the people and systems that act on it without wiring it twice.
Used by these teams
Compare with
Opsgenie
xMatters
ServiceNowOften used alongside
Tools the same teams tend to run next to PagerDuty, across other categories.
AWS Secrets Manager
AppViewX
Azure Key VaultPagerDuty integration FAQ
How do I add a PagerDuty integration to my product?
Enable the PagerDuty connector in your fastn dashboard, then let each customer authenticate their own PagerDuty account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PagerDuty client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PagerDuty account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PagerDuty account and only ever sees their own incidents, alerts and on-call schedules. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this PagerDuty integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which incidents paged overnight, who acknowledged them and what is still open.
Who maintains the PagerDuty integration?
fastn does. When PagerDuty changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How fast does a PagerDuty alert reach my product?
Alerts arrive through event triggers rather than polling, so your product reacts in near real time instead of on a schedule.
Can duplicate or flapping alerts be suppressed?
Yes. Events are deduplicated per incident, so a flapping check does not create a queue of identical records for your users to sift through.
What can I build with the PagerDuty integration?
A common starting point: have each customer authorise their own PagerDuty account, so your product pages their on-call rota instead of emailing an inbox. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the PagerDuty integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PagerDuty does not change your per-connector cost. You can start free with 3 connected accounts.
Add PagerDuty to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.