Website Uptime Monitor with Telegram Alerts

Overview

This workflow periodically pings a website every 5 minutes and sends a Telegram notification whenever the site changes status – from up to down or from down to up. It avoids alert fatigue by only notifying when the state actually changes, rather than spamming you every 5 minutes while the site remains down.

How It Works

1. Schedule Trigger (No auth) – Runs the workflow every 5 minutes.
2. HTTP Request (No auth) – Makes a GET request to the configured URL (e.g., https://esempio.com) with a 10-second timeout and ignores HTTP status errors (so even a 500 or timeout is captured).
3. Code (No auth) – A JavaScript node that stores the previous up/down state in workflow static data. It compares the current status (0 or >=500 = down) with the last known state. If the state hasn't changed, it returns an empty array (no further execution). Only when the state flips does it pass data forward.
4. Telegram (Telegram Bot Token auth) – Sends a message to a pre-configured chat ID. The message includes an emoji (🔴 down / 🟢 up), the HTTP status code (if any), and the timestamp.

Setup Instructions

Prerequisites

• A Telegram account and the Telegram app.
• A Telegram Bot token (get one from @BotFather).
• The chat ID where you want to receive alerts (you can get it by messaging your bot and using the getUpdates API).

Configuration

1. Create a new Telegram credential in n8n with your bot token.
2. Set the environment variable TELEGRAM_CHAT_ID (or replace the placeholder directly in the node parameters).
3. Change the URL in the HTTP Request node to the website you want to monitor.
4. (Optional) Adjust the schedule interval or add more advanced checks (response time, content matching).

Use Cases & Variations

• Monitor any public or internal HTTP endpoint (API, landing page, admin panel).
• Replace Telegram with other notification channels (Slack, email, PagerDuty) by swapping the last node.
• Add logic to alert only after multiple consecutive failures (e.g., 3 down checks in a row) to reduce false alarms.
• Include response time metrics and send a weekly summary report.

This template is ideal for DevOps teams, site reliability engineers, or anyone who needs a lightweight, self-hosted uptime monitor without relying on third-party services.

{
  "name": "Uptime Ping Alert — sai che un sito è giù prima dei tuoi utenti",
  "nodes": [
    {
      "parameters": {
        "rule": {
          "interval": [
            {
              "field": "minutes",
              "minutesInterval": 5
            }
          ]
        }
      },
      "id": "trigger-5m",
      "name": "Ogni 5 minuti",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        0
      ]
    },
    {
      "parameters": {
        "url": "https://esempio.com",
        "options": {
          "timeout": 10000,
          "ignoreHttpStatusErrors": true
        }
      },
      "id": "ping",
      "name": "Chiama il sito",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        220,
        0
      ]
    },
    {
      "parameters": {
        "jsCode": "// Passa in avanti SOLO se lo stato è cambiato rispetto all'ultimo controllo (evita di\n// avvisarti ogni 5 minuti finché il sito resta giù, o su ogni ping quando è su).\nconst state = $getWorkflowStaticData('global');\nconst code = $input.first().json.statusCode || 0;\nconst giu = code === 0 || code >= 500;\nconst eraGiu = state.giu === true;\nif (giu === eraGiu) return [];\nstate.giu = giu;\nreturn [{ json: { giu, code, quando: new Date().toISOString() } }];"
      },
      "id": "filter-change",
      "name": "Solo se cambia stato",
      "type": "n8n-nodes-base.code",
      "typeVersion": 2,
      "position": [
        440,
// ... truncated (copy to see full JSON)