Monitor Your Home Network Free: Uptime Kuma + n8n Alerts

This page may contain affiliate links.

If you run a home server, a Raspberry Pi, or just rely on your Wi-Fi for work, you know the panic of a service going down when you least expect it. Maybe it's your NAS, your Plex server, or that self-hosted dashboard you built. The good news? You don't need a paid monitoring service. Two free, open-source tools — Uptime Kuma and n8n — can watch your network 24/7 and ping you the moment something breaks. Better still, you can chain them together to send alerts to your phone, email, or even a Discord channel, and in some cases trigger automatic recovery. This guide walks you through setting it all up, with exact commands and examples, no enterprise IT budget required.

Why Uptime Kuma and n8n?

Uptime Kuma is a self-hosted monitoring dashboard. It checks whether your websites, IPs, and ports respond, and it does it beautifully — with a slick UI, status pages you can share, and support for HTTP, TCP, ping, DNS, and more. It's the kind of tool that usually costs a fortune, but it's completely free. n8n is a workflow automation tool, like a self-hosted Zapier. You connect triggers (like a webhook) to actions (like sending a message). Together, Uptime Kuma does the watching, and n8n does the telling. The beauty is that both run on a Raspberry Pi or any old PC, so your only cost is a bit of electricity.

Step 1: Get Uptime Kuma Running

If you have Docker, this is a one-liner. On your server or Raspberry Pi, run:

docker run -d --name uptime-kuma -p 3001:3001 -v uptime-kuma-data:/app/data --restart=always louislam/uptime-kuma:1

Then open http://your-server-ip:3001, create an admin account, and you're in. If you don't use Docker, you can install it directly via npm (npm install -g uptime-kuma) or use the Windows installer. Once it's up, click 'Add New Monitor'. For a basic check, pick 'HTTP(s)' and enter the URL of a service you want to watch — say, http://192.168.1.50:8080 for your NAS interface. Set the interval to 60 seconds and choose a nice icon. Do this for all your critical services: your router's admin page, your Pi-hole, your media server, anything that matters.

Step 2: Set Up n8n for Smart Alerts

n8n is just as easy to deploy. With Docker, it's:

docker run -d --name n8n -p 5678:5678 -v n8n-data:/home/node/.n8n --restart=always n8nio/n8n

Open http://your-server-ip:5678 and complete the onboarding. You'll land on a blank workflow canvas. The plan is simple: Uptime Kuma will send a webhook to n8n whenever a monitor goes down or recovers. n8n will then decide what to do — send a push notification, email you, or even restart a Docker container via SSH. First, create a webhook trigger. Drag a 'Webhook' node onto the canvas, set the method to 'POST', and copy the generated URL. That URL is your secret handshake.

Step 3: Connect Uptime Kuma to n8n

Back in Uptime Kuma, edit one of your monitors. Scroll to the 'Notifications' section and click 'Setup Notification'. Choose 'Webhook' from the list. You'll need to configure it carefully. In the 'Webhook URL' field, paste the n8n webhook URL. For the payload, you want to send JSON that n8n can parse. A minimal example:

{"monitorName":"$MONITOR_NAME","status":"$STATUS","down":"true"}

But Uptime Kuma has many variables. I'd recommend sending the full set: $MONITOR_NAME, $STATUS, $DOWN, $PING, $TIMESTAMP. In n8n, the webhook node will capture this as JSON. Now add a 'Switch' node after the webhook to check if body.down equals 'true'. If yes, it's a down alert. If no, it's an up alert. This is where you get clever.

Step 4: Build Your Alert Workflow

For the 'down' branch, add a 'Telegram' node or an 'Email' node. For Telegram, you'll need to create a bot via BotFather and get a chat ID — there are plenty of tutorials. The message could be: '🚨 ALERT: {{ $json.monitorName }} is DOWN. Ping: {{ $json.ping }}ms'. For the 'up' branch, send a calmer message: '✅ {{ $json.monitorName }} is back online.' That's the core workflow. But let's go further. If you have a service that gets stuck, you can use an 'SSH' node in n8n to run a command like docker restart my-container. That turns monitoring into self-healing. Just be careful — don't restart a database willy-nilly. Use a threshold: only auto-restart if it's been down more than 5 minutes. You can add a 'Wait' node for that.

Step 5: Polish and Extend

Once the basics work, you'll want to reduce noise. Nobody wants 50 alerts at 3am. In Uptime Kuma, you can set 'Retries' on each monitor — say, 2 retries with 30 seconds between them. That filters out transient blips. You can also set a 'Maintenance' window in Uptime Kuma so you don't get alerts when you're legitimately rebooting your server. And if you want a public status page for your family or clients, Uptime Kuma has that built in — just create a status page and share the link. It's a lovely touch.

This is the kind of project where the setup can eat an afternoon. If you'd rather skip the trial-and-error, we've put together a Home Lab & Automation Pack — ready-made AI prompts for scripting, troubleshooting and documenting your home lab (from £9). It gives you copy-paste prompts to generate your own n8n workflows, fix Docker issues, and write status page descriptions, so you can get this running in minutes rather than hours.

Hardware Worth Considering

You can run all this on a spare laptop, but a dedicated device is cleaner. A Raspberry Pi 5 (8GB) is ideal — it'll handle Uptime Kuma, n8n, and a few other containers without breaking a sweat. You'll also want a decent microSD card or an SSD for reliability. If you're starting from scratch, grab a Raspberry Pi 5 starter kit — it usually includes the case, power supply, and heatsink, which saves you hunting for parts. For storage, a portable SSD is a solid upgrade over SD cards, especially if you're logging lots of data. And if you want to check your network from outside your home, you'll need to either set up a VPN (Tailscale is free and easy) or port-forward — but that's a topic for another day.

Conclusion

You now have a free, self-hosted monitoring stack that rivals paid services. Uptime Kuma watches your network, n8n turns that data into actionable alerts, and with a little extra effort, you can even automate fixes. The cost is just your time and a few pence of electricity a day. Start with one monitor, get comfortable, then expand. Before long, you'll wonder how you ever lived without knowing the second your Plex server hiccups. And if you want the shortcut, remember the Home Lab pack — it's a fiver well spent for the prompts alone. Happy monitoring.