# PagerDuty Integration
Connect Document360 with PagerDuty to link incident response workflows with operational runbooks and post-mortem documentation.
Overview
The PagerDuty integration enables on-call teams to access relevant Document360 runbooks directly from PagerDuty incidents, accelerating incident response and simplifying post-mortem documentation.
Prerequisites
- A PagerDuty account with service and integration access
- Document360 project admin access
- PagerDuty API key
Setup Steps
- Navigate to Settings → Integrations → PagerDuty in Document360.
- Enter your PagerDuty API key.
- Map PagerDuty services to corresponding Document360 runbook categories.
- Configure webhook triggers for incident events.
- Enable runbook links in PagerDuty incident details.
- Click Save.
Features
- Runbook Links – Surface relevant Document360 runbooks from within PagerDuty incidents.
- Incident Webhooks – Trigger documentation actions based on PagerDuty incident events.
- Post-Mortem Templates – Auto-populate Document360 post-mortem articles with PagerDuty incident data.
- Service Mapping – Map PagerDuty services to specific documentation sections.
Use Cases
- Ensure on-call engineers can access runbooks directly from PagerDuty alerts.
- Automatically create post-mortem documentation drafts from resolved incidents.
- Track which runbooks are accessed during incidents to identify documentation gaps.
Best Practices
- Regularly review runbooks with on-call teams to ensure accuracy and relevance.
- Include runbook links in PagerDuty escalation policies for critical services.
- Conduct blameless post-mortems and capture learnings in Document360 for future reference.
Summary
The PagerDuty integration brings operational documentation into the incident response workflow, enabling faster resolution and continuous improvement through structured post-mortem documentation.