Incident Response Workflow - Part 3

Nodes

9b7d06dc-7e6f-49d5-96e8-7bcc1f77f49921dcce49-0a99-42db-8e94-42561f3e452f896f48b7-b32d-4539-aeba-80f3dfcf68ac9dd572aa-e531-4ffe-a66c-58ac7003ac5d

Categories

Created by

tatanaypant

Last edited 39 days ago

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.

New to n8n?

Need help building new n8n workflows? Process automation for you or your company will save you time and money, and it's completely free!