Skip to main content

Website downtime monitoring with smart alerts via Telegram & Email

Workflow preview

Workflow preview
100%
Website downtime monitoring with smart alerts via Telegram & Email preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Get ==Instant== Alerts When Your Website Goes Down — Using ==n8n== as ==Website Downtime Checker Robot== If you manage websites (your own or clients’), downtime alerts are critical. But most monito...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.switch, n8n-nodes-base.splitout, n8n-nodes-base.merge, n8n-nodes-base.wait, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Muntasir Mubin.

Original n8n.io source

1.1 Workflow description

Title
Website downtime monitoring with smart alerts via Telegram & Email
Workflow name
Website downtime monitoring with smart alerts via Telegram & Email

Get ==Instant== Alerts When Your Website Goes Down — Using ==n8n== as ==Website Downtime Checker Robot==

If you manage websites (your own or clients’), downtime alerts are critical.
But most monitoring tools create alert fatigue — ==emails for every tiny hiccup==, even 30–60 second outages. This setup shows how to use n8n as a smart uptime monitor:
 ✅ No extra subscriptions
 ✅ No false-positive spam
 ✅ Alerts only for real downtime
 ✅ Optional instant phone notifications

Why Use n8n for Website Monitoring? Traditional tools like Uptime Robot become limiting or expensive as you scale. With n8n, you get:

  • Full control over alert logic
  • Custom timing & thresholds
  • No forced notification rules
  • One tool for uptime and other automations You decide when, how, and why alerts are sent.

Quick Start: Free n8n Website Monitoring Workflow Get running in minutes:

  • Use the prebuilt n8n template
  • Sign up for n8n Cloud or self-host for free
  • Set your schedule (default: hourly)
  • Add the websites you want to monitor

Key Setting (Important) Wait time: ==300 seconds (5 minutes)== >Recommended*


If a site goes down, the workflow waits before alerting.
 ➡️ Short hiccups = ignored
 ➡️ Real outages = ==alerted==

How to Test & Use

  1. Activate the workflow
Toggle it on — monitoring runs automatically.
  2. Test instantly
Add a fake or non-existent URL and run the workflow.
After the wait period, you’ll receive an alert.
  3. Stay organized
Alerts arrive cleanly in your inbox
(Tip: pair with an AI email labeling workflow for color-coded alerts)

Get Critical Alerts on Your Phone (Telegram) Email is fine — but critical sites need instant mobile alerts. Best option: Telegram bots

  • Free
  • Fast
  • No extra APIs or subscriptions

How It Works

  • Create a Telegram bot via BotFather
  • Add the bot token & chat ID to n8n
  • Receive downtime alerts instantly on your phone No missed notifications. No noise.

FAQ

  • Can I monitor unlimited sites?
 > ==Yes== — just add more URLs.

  • What about short downtime (seconds)? > Filtered out by the 5-minute wait.

  • Do I need a paid n8n plan?
 > ==No.== Self-hosting is ==free==, and this works on free plans.

  • Why not SMS or WhatsApp?
 > Telegram is ==faster, simpler, and doesn’t require paid APIs.==

📩 Contact Me

If you have any questions, ideas to share, or would like to collaborate on a project, feel free to reach out. I’m always open to meaningful discussions, feedback, and new opportunities.

🔗 ==Connect with me==

💬 You’re welcome to send me a message on any platform, and I’ll get back to you as soon as possible.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - Calculate Status

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.3

Block 3 - Perform Site Test

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 4 - Status Router

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3

Block 5 - Split Out

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 6 - Config

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 7 - Edit Fields

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 9 - Wait

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 10 - Calculate Status1

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.3

Block 11 - Perform Site Test1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 12 - Merge1

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 13 - Status Router1

Type / Role
n8n-nodes-base.switch - switch
Config choices
Version 3

Block 14 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Send a text message

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 17 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note10

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Send email

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

3. Summary Table

Workflow Website downtime monitoring with smart alerts via Telegram & Email
Complexity advanced
Nodes 19
Categories DevOps
Author Muntasir Mubin
Published 13 Dec 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/11763/11763.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Website downtime monitoring with smart alerts via Telegram & Email do?

Get ==Instant== Alerts When Your Website Goes Down — Using ==n8n== as ==Website Downtime Checker Robot== If you manage websites (your own or clients’), downtime alerts are critical. But most monito...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.