Block 1 - Schedule Trigger1
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
Summary This n8n workflow automates Kubernetes root cause analysis (RCA) and incident alerting by integrating with Loki, Prometheus, and Slack. It streamlines log collection, cluster health monitor...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.ssh, n8n-nodes-base.merge, n8n-nodes-base.if, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by John Pranay Kumar Reddy.
Original n8n.io sourceThis n8n workflow automates Kubernetes root cause analysis (RCA) and incident alerting by integrating with Loki, Prometheus, and Slack. It streamlines log collection, cluster health monitoring, and AI-driven RCA with Gemini, saving DevOps teams hours of manual troubleshooting. Designed for production-grade Kubernetes environments, this plug-and-play workflow delivers actionable insights directly to your Slack channels.
π οΈ DevOps Engineers automating Kubernetes monitoring and incident response.
π Site Reliability Engineers (SREs) aiming to reduce mean time to resolution (MTTR).
π Teams using n8n, Slack, Loki, and Prometheus for observability and automation.
π n8 K8s node installed (self-hosted only, see n8n documentation).
π Access to Kubernetes clusters and API.
π Loki and Prometheus set up for log and metrics collection.
π¬ Slack workspace with webhook access for notifications.
π€ Google Gemini AI API key for RCA generation.
DevOps / Monitoring & Observability / Kubernetes/ AI
kubernetes, prometheus, slack, alerting, sre, ops, kube-state-metrics, Gemini, AI
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 36 workflow blocks. Download the JSON for the full node graph.
| Workflow | Kubernetes RCA and alerting using Gemini, Loki, Prometheus, Slack |
|---|---|
| Complexity | advanced |
| Nodes | 36 |
| Categories | AI Summarization, Multimodal AI |
| Author | John Pranay Kumar Reddy |
| Published | 27 Aug 2025 |
Use the JSON export at /data/workflows/7953/7953.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Summary This n8n workflow automates Kubernetes root cause analysis (RCA) and incident alerting by integrating with Loki, Prometheus, and Slack. It streamlines log collection, cluster health monitor...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your AI Summarization, Multimodal AI use case.