PagerDuty
Digital operations management — manage incidents, services, on-call schedules, escalation policies, and send alert events
Three ways to use PagerDuty
Chat with Geni
Ask Geni to pull data, take actions, or answer questions using this integration in a conversation.
Build a workflow
Create automated workflows that trigger on events, run on a schedule, or chain multiple tools together.
Power an app
Use this integration as a data source or action layer behind a dashboard, form, or internal tool.
Supported tools
Actions your AI agents can perform with PagerDuty.
Create Escalation Policy
Create a new escalation policy
Create Incident
Manually create a new incident on a service
Create Incident Note
Post a note to an incident's timeline
Create Service
Create a new service bound to an escalation policy
Create User
Invite a new user to the PagerDuty account
Delete Service
Permanently delete a service
Get started automating PagerDuty
Ready-to-use workflows
Prompts using PagerDuty
Rebuild an incident timeline from Grafana and PagerDuty
Pick a time window and see deploys, alerts, pages and acknowledgements on one merged timeline, then let an agent write the postmortem for you.
Page on-call when a production service goes down on Render
The moment one of your production services fails on Render, your on-call engineer gets paged and the whole team sees it in Slack.
Find which feature flag caused your Sentry error spike
When Sentry alerts on a spiking error, we check every recent feature flag change, rank the likely culprits, and post the top suspects to Slack.
Investigate New Relic alerts before waking your on-call
Every alert gets checked against real error rates, failing transactions and how many servers are hit, so only genuine incidents raise a page.
Alert on-call the moment a Fivetran pipeline breaks
Every 30 minutes we check your Fivetran data pipelines and, the moment one breaks, open a PagerDuty incident and post a Slack heads-up for your on-call team.
Page on-call when a production deploy fails in Buildkite
The moment a build fails on one of your production deploy pipelines, automatically open a PagerDuty incident so on-call gets paged right away.
Auto-retry failed Airbyte syncs before paging on-call
Every 30 minutes, quietly re-run any failed Airbyte sync on a critical connection once, and only page the on-call in PagerDuty and Slack if the retry still fails.
Triage failed Census syncs to PagerDuty, Linear, and Slack
Every 15 minutes, sweep Census for newly failed sync runs, page on-call for outages, file a Linear ticket for config bugs, and log every failure in Slack.
