Automate incident response with Jira, Slack, Google Sheets & Drive
Ready for 3.0What this workflow does
This workflow has 12 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Jira Software, Slack, Google Sheets and Google Drive.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Define Incident Metadata (Edit Fields (Set)): sets 3 fields: service, severity, description
- Combine Incident & Jira Data (Merge): merges the data from its input branches
- Create Jira Incident Ticket (Jira Software): uses Jira Software
- Format Incident Alert for Slack (Code): runs custom JavaScript code
- Validate Jira Ticket Creation Success (If): checks a condition and branches into true / false
- Alert On-Call Team in Slack (Slack): uses Slack
- Log Jira Creation Failures to Error Sheet (Google Sheets): append
- Generate Incident Timeline Report (Code): runs custom JavaScript code
- Convert Timeline to Text File (Convert to File): converts data to a file (to text)
- Log Incident to Status Tracking Sheet (Google Sheets): append
…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 (10)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Jira Software
n8n-nodes-base.jira - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Slack
n8n-nodes-base.slack - Convert to File
n8n-nodes-base.convertToFile - Google Sheets
n8n-nodes-base.googleSheets - Google Drive
n8n-nodes-base.googleDrive - If
n8n-nodes-base.if
From the author
📘 Description: This workflow automates the incident response lifecycle — from creation to communication and archival. It instantly creates Jira tickets for new incidents, alerts the on-call Slack team, generates timeline reports, logs the status in Google…