Manage custom incident response in PagerDuty and Jira
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 14 nodes and runs when an HTTP POST request hits its webhook URL (plus 2 other triggers). Along the way it connects Jira Software, PagerDuty and Mattermost.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 2 other triggers).
- Mattermost: work with channel
- PagerDuty: update (incident)
- PagerDuty: update (incident)
- Mattermost: add user (channel)
- Mattermost: uses Mattermost
- Jira (Jira Software): update
- Jira (Jira Software): uses Jira Software
- Mattermost: uses Mattermost
- Mattermost: uses Mattermost
- Mattermost: uses Mattermost
…plus 1 more step. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Webhook
n8n-nodes-base.webhook - Jira Software
n8n-nodes-base.jira - PagerDuty
n8n-nodes-base.pagerDuty - Mattermost
n8n-nodes-base.mattermost
From the author
This workflow automatically follows the steps in a custom incident response playbook and manages incidents in PagerDuty, Jira tickets, and notifies the on-call team in Mattermost. This workflow consists of three sub-workflows, each automating specific steps…