Triage incidents and enforce SLAs with Gemini, Groq, Google Sheets and Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 36 nodes and runs when an HTTP POST request hits its webhook URL (plus 2 other triggers). Along the way it connects Google Sheets, Google Gemini Chat Model, Groq Chat Model and Slack.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 2 other triggers).
- Accept and Continue (Respond to Webhook): sends the response back to the webhook caller
- Log Acknowledgment (Google Sheets): update
- Log Human Feedback (Google Sheets): update
- Normalize Incident Data (Edit Fields (Set)): sets 8 fields: incidentId, title, description…
- Ack Response (Respond to Webhook): sends the response back to the webhook caller
- Feedback Response (Respond to Webhook): sends the response back to the webhook caller
- Fetch Runbook Context (Google Sheets): uses Google Sheets
- Build Runbook Context (Code): runs custom JavaScript code
- Agent 1 - Incident Analyzer (AI Agent): runs an AI agent, with model: Analyzer LLM (Gemini), Analyzer Fallback (Groq)
- Parse Analyzer Output (Code): runs custom JavaScript code
…plus 19 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 (12)
- Webhook
n8n-nodes-base.webhook - Respond to Webhook
n8n-nodes-base.respondToWebhook - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - Code
n8n-nodes-base.code - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Groq Chat Model
@n8n/n8n-nodes-langchain.lmChatGroq - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack - If
n8n-nodes-base.if - Wait
n8n-nodes-base.wait
From the author
Reduce MTTR with context-aware AI severity analysis and automated SLA enforcement Know that feeling when a "low priority" ticket turns into a production fire? Or when your on-call rotation starts showing signs of serious burnout from alert overload? This…