Monitor service uptime and send incident alerts via HTTP checks and Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on a schedule (every 5 minutes). Along the way it connects Telegram.
How it runs
Trigger: On a schedule (every 5 minutes).
- Config (Edit Fields (Set)): sets 3 fields: url, serviceName, chatId
- Check Endpoint (HTTP Request): calls an HTTP API
- Is Down? (If): checks a condition and branches into true / false
- Alert Telegram (Telegram): uses Telegram
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Quick overview This workflow runs every five minutes to check a configured health URL and sends a Telegram alert when the endpoint returns an HTTP error status. How it works 1. Runs every 5 minutes on a schedule. 2. Loads the target URL, service name, and…