Incident response workflow - Part 3
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.
Nodes used (4)
- Mattermost
n8n-nodes-base.mattermost - Jira Software
n8n-nodes-base.jira - PagerDuty
n8n-nodes-base.pagerDuty - Webhook
n8n-nodes-base.webhook
What it does
This workflow is the third of three. You can find the other workflkows here: 1. Incident Response Workflow - Part 1 2. Incident Response Workflow - Part 2 3. Incident Response Workflow - Part 3 We have the following nodes in the workflow: 1. Webhook node: This trigger node listens to the event when the Resolve button is clicked. 2. PagerDuty node: This node changes the status of the incident report from Acknowledged to Resolved in PagerDuty. 3. Jira Software node: This node moves the incident issue to Done. 4. Mattermost node: This node publishes a message in the auxiliary channel mentioning that the incident has been marked as resolved in PagerDuty and Jira. 5. Mattermost node: This node publishes a message in the specified Incidents channel that the incident has been resolved by the on-call team.