The Helper Chain

A serverless function running on Cloudflare's edge network. Every six hours, a cron trigger fires it automatically. It makes HTTP requests to five websites, checks whether each responds and returns a healthy status code, then passes the results downstream. No server to manage, no uptime to worry about — it runs on Cloudflare's infrastructure.

Cloudflare's serverless SQL database. Created with a single CLI command, it stores every health check result with a timestamp. This persistence means you can track patterns over time — not just "is it down now?" but "how often does it go down?" The Worker writes to it via a binding, no connection strings or credentials to manage.

An automation platform that receives webhook events and decides what to do with them. When a site is down, the Worker sends a POST request to an n8n webhook URL. n8n receives the JSON payload, formats it into a human-readable alert, and routes it to Telegram. It's the traffic controller — it doesn't generate the data or deliver the message, it connects the two.

The final mile. A Telegram bot receives the formatted alert from n8n and delivers it as a message. The alert arrives on your phone within seconds of the health check failing. Zero human intervention from trigger to notification — the entire chain runs autonomously.