Skip to product information

n8n HTTP Uptime Monitor Workflow + Telegram Incident Alerts

n8n HTTP Uptime Monitor Workflow + Telegram Incident Alerts

 (200+Reviews)
Regular price £31.99
Regular price £31.99 Sale price
SAVE Sold out
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
🔥
128+ Sold
Popular with n8n builders
âš¡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n HTTP Uptime Monitor Workflow + Telegram Incident Alerts

n8n HTTP Uptime Monitor Workflow + Telegram Incident Alerts

Regular price £31.99
Regular price £31.99 Sale price
SAVE Sold out

Never miss an outage: HTTP Uptime checks every 5 minutes with Telegram alerts

This n8n HTTP Uptime Monitor Workflow continuously checks your configured health URL and immediately sends a Telegram incident alert whenever the endpoint returns an HTTP error status (greater than 399). When everything is healthy, it stays quiet.

What this workflow does

  • Runs every 5 minutes using an n8n schedule trigger.
  • Loads configuration (target URL, service name, and Telegram chat ID) from a dedicated configuration step—either by editing the node inputs or mapping to environment variables: HTTP_URL, SERVICE_NAME, and TELEGRAM_CHAT_ID.
  • Sends an HTTP request to the health URL with a 10-second timeout, capturing the full response without failing the workflow on errors.
  • Evaluates the HTTP status code: if the status is > 399, the service is treated as failed.
  • Posts a Markdown Telegram message including the service name, status code, URL, and the check timestamp.
  • Ends silently on success (no alert is sent when the status indicates the service is up).

Use cases

  • Monitor critical SaaS endpoints (e.g., health or readiness URLs) and get instant Telegram notifications.
  • Catch upstream downtime early by alerting on non-2xx/3xx HTTP responses.
  • Provide lightweight uptime monitoring for self-hosted services without adding a dedicated monitoring stack.

Technical details

  • Workflow schedule: every 5 minutes.
  • HTTP check: HTTP Request node with 10-second timeout; workflow continues even on errors.
  • Alerting: Telegram node with Markdown-formatted messages.
  • Logic nodes: if, set, no op, plus supportive nodes like sticky note.

Setup requirements

  • n8n (self-hosted or cloud), built and tested on 2.35.x.
  • A Telegram bot token created via BotFather and added as an n8n Telegram credential.

Customization: Adjust the interval in the Schedule Trigger, expand the Config node to monitor multiple services, or replace Telegram with Slack, Discord, or email.

Also published as a free, MIT-licensed workflow with setup notes.

View full details