One Morning Message Grades Every Home Server: An n8n Check Caught a Crashed fail2ban and NAS Drives at 86% on Day One
- Level Advanced
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeNo
What did they do with n8n?
He wanted one message every morning telling him whether his home servers were OK, without running a full monitoring stack. His n8n workflow runs at 7 AM, logs into each server over SSH with a small read-only script, and one code step grades every server green, yellow or red. It checks disk space on every drive including NAS shares, memory, stopped Docker containers, failed system services, pending updates and whether a reboot is needed. A server that can't be reached shows up red instead of quietly dropping off the report. Everything goes out as one Slack or Discord message. He says the first run caught a crashed fail2ban security service on his Proxmox host and NAS mounts at 86% full.
How it went
n8n community 'Built with n8n' post by @WizenTom (Nov 8, 2026 UTC): Schedule -> chained SSH nodes -> one Code node -> Slack webhook (Discord option); read-only POSIX probe prints JSON; grades disk, memory, stopped containers, failed systemd units, pending updates, reboot-required; unreachable hosts reported red. First run caught a crashed fail2ban on his Proxmox host and NAS mounts at 86%. Tested on Debian, Ubuntu, Proxmox VE and Arch. Built with help from Claude. He links a packaged version for people who don't want to build it
Worth knowing
- n8n community 'Built with n8n' post by @WizenTom (Nov 8, 2026 UTC): Schedule -> chained SSH nodes -> one Code node -> Slack webhook (Discord option); read-only POSIX probe prints JSON; grades disk, memory, stopped containers, failed systemd units, pending updates, reboot-required; unreachable hosts reported red. First run caught a crashed fail2ban on his Proxmox host and NAS mounts at 86%. Tested on Debian, Ubuntu, Proxmox VE and Arch. Built with help from Claude. He links a packaged version for people who don't want to build it.
Prompt
Cleaned version rewritten from the source — not a direct quote.
Help me build a daily server health check. Every morning at [time], connect to each of these servers: [list] using a read-only script that changes nothing. For each one, report disk use on every drive, memory, stopped containers, failed services, pending updates and whether a reboot is needed. Grade each server green, yellow or red using these thresholds: [warn % / critical %]. If a server can't be reached, mark it red and say so instead of leaving it out. Send everything as ONE message to [Slack or Discord channel].
Recommended
Try it in Grok Bot
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (Google Drive, Slack, Discord) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in n8n, Claude, ChatGPT Agent, OpenClaw.
Set it up
Tools: Google Drive, Slack, Discord · Stack: n8n + Claude (used to build it)
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
n8n community 'Built with n8n' post by @WizenTom (Nov 8, 2026 UTC): Schedule -> chained SSH nodes -> one Code node -> Slack webhook (Discord option); read-only POSIX probe prints JSON; grades disk, memory, stopped containers, failed systemd units, pending updates, reboot-required; unreachable hosts reported red. First run caught a crashed fail2ban on his Proxmox host and NAS mounts at 86%. Tested on Debian, Ubuntu, Proxmox VE and Arch. Built with help from Claude. He links a packaged version for people who don't want to build it (as of 2026-11-12)
Source: Web · Verified by us: not yet · Report broken or outdated