Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
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...
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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Muntasir Mubin.
Original n8n.io sourceGet ==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:
Quick Start: Free n8n Website Monitoring Workflow Get running in minutes:
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
Get Critical Alerts on Your Phone (Telegram) Email is fine — but critical sites need instant mobile alerts. Best option: Telegram bots
How It Works
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.
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.
| Workflow | Website downtime monitoring with smart alerts via Telegram & Email |
|---|---|
| Complexity | advanced |
| Nodes | 19 |
| Categories | DevOps |
| Author | Muntasir Mubin |
| Published | 13 Dec 2025 |
Use the JSON export at /data/workflows/11763/11763.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
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...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.