PagerDuty
Incident management workflows for PagerDuty REST API v2.
Connect it
In Keystile Automations → Connections → New connection, choose PagerDuty and sign in. Your AI tools and workflows then use it through Keystile; they never see the password or key.How connecting works.
Try it from your AI tool
Using Keystile, in PagerDuty: acknowledge incident (Acknowledge an existing PagerDuty incident).What it can do (6 actions)
| Action | What it does | Changes data |
|---|---|---|
| Acknowledge Incident | Acknowledge an existing PagerDuty incident. | |
| Create Incident | Create a new PagerDuty incident using the REST API. | |
| Custom API Call | Make a custom API call to PagerDuty REST API v2. Authorization, Accept, and Content-Type headers are injected automatically. For write endpoints that require a From header, add it manually in the headers field. | Yes |
| Get Incident | Retrieve a PagerDuty incident by ID. | |
| List Incidents | List PagerDuty incidents with optional filters and pagination. | |
| Resolve Incident | Resolve an existing PagerDuty incident. |
Start a workflow when… (3 triggers)
- New Incident — Triggers when a new incident is created
- Incident Resolved — Triggers when an incident is resolved.
- Incident Acknowledged — Triggers when an incident is acknowledged.
How Keystile protects it
Every PagerDuty action is checked before it runs, whether it comes from an AI tool or a workflow. 1 of its actions change data; your rules, limits and budgets decide whether each is allowed, held for a person or stopped, and it all goes into the signed record.
Use PagerDuty with your AI assistant — safelyClaude, Cursor or ChatGPT do the work; Keystile checks every action first.
Get early access