Automate Incident Management with PagerDuty, Port AI, Jira & Slack
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: OpenAI (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| OpenAI (legacy) Assess Severity, Generate Post-Mortem Template | OpenAI node (AI section) |
Community nodes
These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
CUSTOM(Extract Context (New Incident), Parse Context (New Incident), Extract Context (Resolved), Parse Context (Resolved), Schedule Post-Mortem via Port, Parse Schedule Response, Log MTTR to Port)
Nodes used (7)
- Webhook
n8n-nodes-base.webhook - Switch
n8n-nodes-base.switch - Port Io
CUSTOM.portIo - OpenAI
n8n-nodes-base.openAi - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Jira Software
n8n-nodes-base.jira
What it does
Complete incident workflow from detection through resolution to post-mortem, with full organizational context from Port's catalog. This template handles both incident triggered and resolved events from PagerDuty, automatically creating Jira tickets with context, notifying teams via Slack, calculating MTTR, and using Port AI Agents to schedule post-mortem meetings and create documentation. How it works The n8n workflow orchestrates the following steps: On Incident Triggered: - PagerDuty webhook — Receives incident events from PagerDuty via POST request. - Event routing — Routes to triggered or resolved flow based on event type. - Port context enrichment — Uses Port's n8n node to query your software catalog for service context, on-call engineers, recent deployments, runbooks, and past incidents. - AI severity assessment — OpenAI assesses severity based on Port context and recommends investigation actions. - Escalation routing — Critical incidents automatically escalate to leadership Slack channel. - Jira ticket creation — Creates incident ticket with full context, investigation checklist, and recommended actions. - Team notification — Notifies the team's Slack channel with incident details and resources. On Incident Resolved: - Port context extraction — Gets post-incident context from Port including stakeholders and documentation spaces. - MTTR calculation — Calculates mean time to resolution from incident timestamps. - Post-mortem generation — AI generates a structured post-mortem template with timeline. - Port AI Agent scheduling — Triggers Port AI Agent to schedule post-mortem meeting, invite stakeholders, and create documentation. - Resolution notification — Notifies team with MTTR, post-mortem document link, and meeting details. - Metrics logging — Logs MTTR metrics back to Port for service reliability tracking. Setup - Register for free on Port.io - Configure Port with services, on-call schedules, and deployment history - Set up Port AI agents for post-mortem scheduling - Connect PagerDuty webhook for incident events - Configure Jira project for incident tickets (use project key 'INC' or customize) - Set up Slack channels for alerts (incidents and leadership-alerts) - Add OpenAI credentials for severity assessment - Test with a sample incident event - You should be good to go! Prerequisites - You have a Port account and have completed the onboarding process. - Port's integrations are configured (GitHub, Jira, PagerDuty if available). - You have a working n8n instance (Cloud or self-hosted) with Port's n8n custom node installed. - PagerDuty account with webhook capabilities. - Jira Cloud account with appropriate project permissions. - Slack workspace with bot permissions to post messages. - OpenAI API key for severity assessment and post-mortem generation. ⚠️ This template is intended for Self-Hosted instances only.