FM
FlowMarket
DevOps & GitHub Beginner ⚡ 5 n8n Nodes

Incident response workflow - Part 3

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....

🔌 Nodes & Integrations Used (3)

Mattermost Jira Pager Duty

📖 Implementation & Setup Guide

This workflow is the third of three. You can find the other workflkows here:

  1. [Incident Response Workflow - Part 1](https://n8n.io/workflows/353)
  2. [Incident Response Workflow - Part 2](https://n8n.io/workflows/354)
  3. [Incident Response Workflow - Part 3](https://n8n.io/workflows/355)

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.

⚡ How to import this workflow into n8n:

  1. Click the Direct Download JSON button above to save Incident response workflow - Part 3.json.
  2. Log in to your n8n Cloud or self-hosted n8n instance.
  3. In your workflow canvas, click the menu in top-right and select Import from File (or paste the JSON directly).
  4. Configure your credentials (e.g. API keys, database URLs) in the corresponding node settings.
  5. Click Execute Workflow to test and switch to Active!

Related DevOps & GitHub Workflows

View All in DevOps & GitHub →