Zenning for PagerDuty
Zenning can summarise an incident, flag repeat incidents and brief you on who's on call.
Surface incidents and on-call gaps
What Zenning can do
- Draft an incident recap
- Spot alert noise
- Track time to respond
Try asking
Weekly review PagerDuty on-call coverage, sync runbooks from Notion, and confirm escalation paths in Slack.
What it does in PagerDuty
- When a critical alert fires in SentryCheck related logs in New Relic, create a Linear ticket and notify the security Slack channel with suggested remediation
- After a PagerDuty incident resolvesDocument the timeline in Notion, link follow-up tasks in Linear, and share postmortem notes in Slack
- When customers report outages during a PagerDuty incidentUpdate Intercom macros from Notion and reply with ETA via Gmail
Triggers
The PagerDuty events that can start a workflow.
13 triggers
- Incident Acknowledged
- Incident Delegated
- Incident Escalated
- Incident Note Added
- Incident Priority Updated
- Incident Reassigned
- Incident Reopened
- Incident Resolved
- Incident Triggered
- Incident Unacknowledged
- Responder Added
- Responder Replied
- Status Update Published
Connect PagerDuty in a few minutes
Connect it in a few clicks and choose who in your team can use it. Change that any time.