Server Uptime Monitor in n8n: HTTP Checks + Data Table

Instant HTTP uptime checks + Telegram alerts, powered by n8n Data Table

This n8n workflow monitors one or more URLs every minute, records each latest HTTP response status code in an n8n Data Table, and sends Telegram notifications when a server goes down/up or when a condition persists beyond a configured interval.

What this workflow does

• Runs manually or on a schedule (every minute).
• Builds a monitoring list containing each URL, the Data Table name, and a notification interval.
• Performs an HTTP request to each URL and captures the response status code.
• Fetches the last saved status code for that URL from the specified n8n Data Table and merges it with the current check result.
• If the HTTP status code changed, it triggers a separate workflow to send a Telegram notification about the change.
• If the status code stays the same, it checks whether the last update is older than the configured interval; if so, it triggers a separate workflow to send a “still down/up” Telegram message.
• Upserts the current HTTP status code back into the n8n Data Table for the next run.

Use cases

• Monitor SaaS endpoints (health pages, APIs, webhooks) and alert your team via Telegram.
• Detect regressions quickly by tracking status changes and repeatedly notifying only after a persistence interval.
• Centralize uptime state using an n8n Data Table for easy visibility and auditability.

Technical details

• Nodes/logic referenced: if, set, code, merge, data table, sticky note.
• HTTP checks collect HTTP response status codes.
• Persistence stored in an n8n Data Table (example: server_status with url and http_response_code fields).
• Telegram alerts are sent by a separate called workflow; ensure Telegram credentials are configured and the workflow accepts a message input.

Designed for reliable server uptime monitoring in n8n, this workflow keeps your alerts accurate, timely, and state-aware.