I built a n8n health monitoring workflow
My n8n crashed overnight and took 89GB of disk with it.
Updated n8n. Went to bed. Woke up to:
- Server unreachable
- Disk: 28GB → 89GB
- 3.8 million executions in 24 hours
- 43 workflows dead
One routine update. Complete disaster.
Recovery: Diagnosed via SSH, cleaned the database, reclaimed 60GB — back online without losing a single workflow.
But the scariest part wasn't the crash.
It was that I had no visibility of running workflows
So I built a workflow that monitors all my other workflows.
Every night at 5 PM — one email:
- n8n online or down?
- Disk usage
- Executions + errors
- Status of all 43 workflows
30 minutes of daily manual checking → 0
4-hour crisis → 15-minute early fix
Three things to do if you self-host n8n:
- Enable execution pruning — unchecked history will fill your disk silently
- Check logs after every update
- Build a monitoring workflow before you need one
Drop a comment if you want the workflow JSON. 👇
6
0 comments
I built a n8n health monitoring workflow
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
1
+5457
2
🔥
+2807
3
+1539
4
+1351
5
🔥
+976
Powered by