Monitor Kubernetes services & pods with Prometheus and send alerts to Slack

by John Pranay Kumar Reddy ✓ · 1,147 views · created 2025-08-20 · DevOps, Multimodal AI

What this workflow does

This workflow has 16 nodes and runs on a schedule (every minute). It uses only n8n's built-in nodes. It also calls prometheus-kube-prometheus-prometheus.monitoring:9090 and slack.com over HTTP.

How it runs

Trigger: On a schedule (every minute).

1. Current endpoints (HTTP Request): calls prometheus-kube-prometheus-prometheus.monitoring:9090
2. Endpoints 5m ago (HTTP Request): calls prometheus-kube-prometheus-prometheus.monitoring:9090
3. Pods Running State (HTTP Request): calls prometheus-kube-prometheus-prometheus.monitoring:9090
4. Containers Not Ready (HTTP Request): calls prometheus-kube-prometheus-prometheus.monitoring:9090
5. CrashLoopBackOff / Termination Reason (HTTP Request): calls prometheus-kube-prometheus-prometheus.monitoring:9090
6. Pod Restart Spike (last 5m) (HTTP Request): calls prometheus-kube-prometheus-prometheus.monitoring:9090
7. Pod Pending State (HTTP Request): calls prometheus-kube-prometheus-prometheus.monitoring:9090
8. Map Prometheus results into namespace/service (Code): runs custom JavaScript code
9. Map Prometheus results into namespace/service (Code): runs custom JavaScript code
10. Merge: merges the data from its input branches

…plus 5 more steps. See the full node list below.

HTTP calls to: prometheus-kube-prometheus-prometheus.monitoring:9090, slack.com

Before you upgrade to n8n 3.0

Nodes used (4)

• Schedule Triggern8n-nodes-base.scheduleTrigger
• HTTP Requestn8n-nodes-base.httpRequest
• Coden8n-nodes-base.code
• Mergen8n-nodes-base.merge

From the author

🧩 Short Summary Proactively alert to service endpoint changes and pod/container issues (Pending, Not Ready, Restart spikes) using Prometheus metrics, formatted and sent to Slack. 🗂️ Category DevOps / Monitoring & Observability 🏷️ Tags kubernetes,…

View the original on n8n.io → Check your own copy