Analyze alerts from Alertmanager and send diagnostic reports to 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 14 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects OpenAI Chat Model, MCP Client, Qdrant Vector Store and Embeddings Google Gemini and 1 more.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- SetVars (Edit Fields (Set)): sets 2 fields: prometheus_uid, loki_uid
- PreProcessAlerts (Code): runs custom JavaScript code
- AI Agent: runs an AI agent, with model: OpenAI Chat Model; 5 tools (K8S mcp, Gitlab MCP, Grafana mcp, Digitalocean MCP…)
- GetAlertMessages (Slack): history (channel)
- FindAlert (Code): runs custom JavaScript code
- SendReport (Slack): uses Slack
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 (9)
- AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - MCP Client Tool
@n8n/n8n-nodes-langchain.mcpClientTool - Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - Qdrant Vector Store
@n8n/n8n-nodes-langchain.vectorStoreQdrant - Embeddings Google Gemini
@n8n/n8n-nodes-langchain.embeddingsGoogleGemini - Slack
n8n-nodes-base.slack - Edit Fields (Set)
n8n-nodes-base.set
From the author
Overview This workflow helps automatically analyze alerts occurring in the infrastructure and suggest solutions even before the on-duty engineer sees the alert. How It Works The workflow receives an alert from Alertmanager via Webhook. The variables required…