Automated Incident Resolution and Notification
detail.loadingPreview
Automate the resolution of PagerDuty incidents and update Jira tickets, then notify relevant teams via Mattermost.
About This Workflow
This workflow automates the process of resolving incidents triggered by PagerDuty and updating corresponding Jira tickets. Once an incident is resolved in PagerDuty, the workflow automatically marks the associated Jira issue as resolved and sends notifications to a specified Mattermost channel. This ensures timely updates and efficient incident management.
Key Features
- Automated PagerDuty Incident Resolution: Automatically resolves incidents in PagerDuty based on incoming webhook data.
- Jira Ticket Update: Updates the status of a Jira issue to 'resolved' using its key.
- Mattermost Notifications: Sends customizable messages to Mattermost channels upon successful resolution and update.
How To Use
- Trigger: The workflow is triggered by a webhook. Ensure your external system (e.g., PagerDuty or a custom integration) sends a POST request to the provided webhook URL.
- Data Input: The webhook payload should contain
body.context.pagerduty_incidentfor the PagerDuty incident ID andbody.context.jira_keyfor the Jira issue key. It also needsbody.channel_idfor the Mattermost notification. - PagerDuty Node: This node receives the PagerDuty incident ID from the webhook and sets its status to 'resolved'.
- Jira Node: This node uses the Jira key from the webhook to update the status of the corresponding Jira issue to '31' (assuming '31' is the ID for 'Resolved' or a similar status).
- Mattermost Nodes: Two Mattermost nodes are configured:
- The first node sends a generic notification to a specific channel (
k1h3du9r9byyfg7sys8ib6p3ey) about the resolved incident, referencing the PagerDuty summary. - The second node (which appears to be intended for a different notification based on its message) also sends a message to a Mattermost channel using the
channelIdprovided by the webhook. This node is configured to send a message indicating that the issue was closed in PagerDuty and Jira.
- The first node sends a generic notification to a specific channel (
Apps Used
Workflow JSON
{
"id": "e428f2e1-d668-4187-8ddf-25f352497e8e",
"name": "Automated Incident Resolution and Notification",
"nodes": 11,
"category": "Automation",
"status": "active",
"version": "1.0.0"
}Note: This is a sample preview. The full workflow JSON contains node configurations, credentials placeholders, and execution logic.
Get This Workflow
ID: e428f2e1-d668...
About the Author
Crypto_Watcher
Web3 Developer
Automated trading bots and blockchain monitoring workflows.
Statistics
Related Workflows
Discover more workflows you might like
Inventory Slack Alert Workflow
Triggers an alert based on inventory changes, processes data using RAG, and logs results.
Automated Google Drive Backup for n8n Workflows
Automatically back up n8n workflows to Google Drive on a schedule.
Supply Chain Delay Monitor
Automated monitoring and logging of supply chain delays using a webhook, text processing, embeddings, and a vector store.