Triage and remediate Kubernetes incidents using Claude and Slack
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) AI Agent - Diagnose Root Cause & Propose Remediation (v1.6), AI Agent - Verify Symptoms Resolved (v1.6) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (10)
- Webhook
n8n-nodes-base.webhook - Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - AI Agent
@n8n/n8n-nodes-langchain.agent - Anthropic Chat Model
@n8n/n8n-nodes-langchain.lmChatAnthropic - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Wait
n8n-nodes-base.wait
What it does
Quick overview This workflow receives Kubernetes failure alerts via a webhook, collects diagnostics from a kubectl wrapper API, uses Anthropic Claude to propose a remediation with a risk level, requests approval in Slack when needed, executes the action via an API, then verifies recovery and either logs closure or escalates. How it works 1. Receives an Alertmanager/Kubernetes failure alert via a webhook (or runs manually for testing) and normalizes the target cluster, namespace, and resource details. 2. Calls a Kubernetes diagnostics wrapper API to gather recent events, logs, resource usage, and workload state for the affected resource. 3. Sends the diagnostic snapshot to Anthropic Claude to generate a root-cause hypothesis and a single proposed remediation action with a Safe vs NeedsApproval risk level. 4. Automatically executes the remediation via a Kubernetes action wrapper API when it is marked Safe and on the allowlist, otherwise posts the proposal to Slack and waits for an approval response. 5. After execution, waits for a stabilization period, re-collects diagnostics, and asks Anthropic Claude to verify whether the original symptoms are resolved. 6. Logs the incident as resolved to an incident log API when the cluster is healthy, or escalates the full context to a Slack escalation channel when it is not. Setup 1. Provide an Anthropic credential (Claude) and update the model selection if you don’t want to use the configured default. 2. Create HTTP Header Auth credentials for your Kubernetes diagnostics API, Kubernetes action API, and incident log API, then replace the three API base URLs in the configuration values. 3. Add a Slack credential and set the approval and escalation channel names to match your workspace. 4. Configure Alertmanager (or your alert source) to send POST requests to the workflow webhook URL with cluster/namespace/resource fields, and ensure your approval process can resume the wait step with an approved=true or approved=false payload.