Draft and track incident postmortems with OpenAI, Google Sheets, Discord and Gmail
Ready for 3.0What this workflow does
This AI workflow has 30 nodes and runs on a schedule (cron 0 9 1 * *) (plus 2 other triggers). Along the way it connects Gmail, OpenAI Chat Model, Google Sheets and Discord and 1 more.
How it runs
Trigger: On a schedule (cron 0 9 1 * *) (plus 2 other triggers).
- Read Postmortems (Google Sheets): uses Google Sheets
- Normalize Incident Data (Edit Fields (Set)): sets 12 fields: incident_id, received_at, status…
- Read Open Action Items (Google Sheets): uses Google Sheets
- Filter Current Month (Code): runs custom JavaScript code
- Validate Incident Input (If): checks a condition and branches into true / false
- Prepare Weekly Follow-up (Code): runs custom JavaScript code
- Summarize Monthly RCA Trends (AI Agent): runs an AI agent, with model: OpenAI Monthly RCA Model
- Acknowledge Reporter by Email (Gmail): uses Gmail
- Alert Invalid Report on Discord (Discord): work with message
- If: checks a condition and branches into true / false
…plus 15 more steps. 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 (11)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - Discord
n8n-nodes-base.discord - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Telegram
n8n-nodes-base.telegram
From the author
Incidents become lessons automatically. This workflow takes incident reports from a form, has AI draft a structured postmortem with root cause and action items, logs everything to Sheets, and keeps stakeholders posted. Overdue actions get chased weekly,…