Manual incident triage kills your MTTR. This workflow automates the first response so your engineers get actionable tickets instead of raw alerts.
Mattermost Pagerduty. Uses jira, pagerDuty, mattermost. Webhook trigger; 14 nodes.
PagerDuty:incident:create get update getAll:incidentNote:create getAll:User:get:LogEntry:getAll get. Uses start, pagerDuty. Manual trigger; 11 nodes.
Smart Factory Use Case. Uses amqpTrigger, crateDb, pagerDuty, noOp. Event-driven trigger; 9 nodes.
Flow. Uses httpRequest, slack, pagerDuty. Scheduled trigger; 7 nodes.
Mattermost. Uses mattermost, jira, pagerDuty. Webhook trigger; 5 nodes.
01.07 Crypto Treasury Real-Time P&L Tracking. Uses httpRequest, notion, pagerDuty. Webhook trigger; 5 nodes.
Create, update, and get an incident on PagerDuty. Uses manualTrigger, pagerDuty. Event-driven trigger; 4 nodes.
Mattermost Pagerduty. Uses pagerDuty, mattermost. Webhook trigger; 3 nodes.
9 of 9 workflows in this view · Browse all →
FAQ
How many n8n Pagerduty workflows are in the catalog?
9 n8n workflows in AutomationFlows currently use the Pagerduty integration — triggers, actions, or both.
How do I connect Pagerduty in n8n?
After importing the workflow JSON, n8n will prompt for Pagerduty credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most Pagerduty workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.