How to Monitor Website Uptime and Alert via Telegram with n8n

11 May 2026 — 4 min read

Downtime costs money. Every minute your site is unreachable, you're losing leads, sales, and trust — and in most cases, you find out from a client before your monitoring tool tells you. There's a better way: a simple n8n workflow that pings your site every few minutes and fires a Telegram message the moment something breaks. No paid uptime service. No extra subscriptions. Just an automation that runs silently in the background and screams when it needs to.

Why n8n for Uptime Monitoring

Most uptime monitoring tools charge a monthly fee for what is fundamentally a cron job plus an HTTP request. n8n gives you the same capability with full control over alert content, retry logic, and notification channels. If you're already running n8n — whether self-hosted or on n8n Cloud — adding uptime monitoring is a 15-minute job. And because it's a workflow, you can extend it: log downtime to a Google Sheet, notify multiple channels, or trigger a recovery script automatically.

Runs on any schedule — every 1, 2, or 5 minutes
Works with any HTTP-accessible URL
Sends rich Telegram messages with status code, timestamp, and response time
Zero external dependencies beyond n8n itself

How the Workflow Works

The logic is straightforward. A Schedule trigger fires at your chosen interval. An HTTP Request node sends a GET request to your target URL. An IF node checks the response: if the status code is outside the 200–299 range, or if the request times out, the workflow branches to an error path. That path sends a Telegram message with the alert details. If everything is fine, the workflow ends silently — no noise when things are working.

Schedule Trigger — set to every 2 minutes for near-realtime detection
HTTP Request — GET to your URL, with a timeout of 10 seconds and error handling set to "continue on fail"
IF node — checks {{ $json.statusCode }} is not between 200 and 299, or {{ $json.error }} exists
Telegram node — sends message to your bot with site name, status code, and UTC timestamp

One important detail: set the HTTP Request node to continue on failure rather than stop the workflow. If the site is completely down, the request throws an error — and without "continue on fail" enabled, your IF node never runs and you never get alerted. Always handle the timeout case explicitly.

Setting Up the Telegram Alert

You'll need a Telegram bot and a chat ID. Create a bot via @BotFather in Telegram, grab the token, then add the bot to a personal chat or group and retrieve the chat ID by calling the Telegram getUpdates API endpoint. In n8n, add a Telegram credential with your bot token and you're ready.

Format your alert message to include everything you need at a glance when you wake up to a notification at 3am:

Site name and URL
HTTP status code (or "timeout / unreachable")
Timestamp in UTC
Response time in milliseconds (available from the HTTP node output)

A message like "🔴 yoursite.com DOWN — Status 503 — 2026-06-17 04:12 UTC — Response: 12043ms" gives you everything you need without opening a dashboard. You can also add a second Telegram message on recovery — when the next check succeeds after a failure — by storing the last status in a static data node or an external variable.

Extending the Workflow

Once the core loop is working, a few additions make it production-grade. First, add debouncing: track consecutive failures before alerting, so a single blip doesn't wake you up. Two or three consecutive failures before firing the Telegram message eliminates false positives from transient network issues. Second, log every check result — status code, response time, timestamp — to a Google Sheet or Airtable. After a week, you have a latency baseline and can spot degradation before it becomes downtime. Third, monitor multiple URLs in the same workflow using a split-in-batches approach, so one scheduler covers your entire infrastructure.

If you want to skip the build-it-yourself path and get a workflow that's already structured, tested, and ready to import, there are ready-made n8n templates built specifically for operational use cases like this — no starting from a blank canvas.

Uptime monitoring is one of those automations that pays for itself the first time it catches an outage before your clients do. The workflow is simple enough to build in an afternoon, and once it's running, it requires zero maintenance. Set it up once, forget it's there, and let it do exactly one job: tell you when something breaks.