n8n URL Uptime Monitor with Data Tables & SMTP Alerts

Monitor URL uptime every 5 minutes—confirm downtime with 2 failures and get SMTP alerts + daily reports

This n8n workflow continuously checks your URLs on a 5-minute schedule, only confirms downtime after two consecutive failures, and sends clear SMTP email alerts when a site goes DOWN or recovers—while logging every check to n8n Data Tables and emailing a daily uptime/latency report at 08:00.

What this workflow does

• Scheduled monitoring: Runs every 5 minutes to load recent incident history and recent check results from n8n Data Tables.
• Per-URL probing with retry: Builds a per-URL check list (including expected page text and the previous state) and performs an HTTP GET. If the first attempt fails, it retries once after a short wait.
• Downtime confirmation logic: Detects confirmed downtime only after two consecutive failed checks. Detects recovery on the first successful check after being down and calculates downtime minutes.
• Persistent logging: Records every check outcome (status code, response time, and reason) to the url_checks Data Table.
• Incident + notification: On state change, writes an incident to the url_incidents table and sends a single SMTP email alert for either DOWN or RECOVERED.
• Daily HTML report: At 08:00, aggregates the last 24 hours of checks (compared to the prior 24 hours) and emails an HTML report with uptime %, average and p95 response times, and incidents per URL.
• Automatic cleanup: Deletes url_checks rows older than 14 days to keep your dataset lean.

Use cases

• SaaS teams monitoring critical endpoints (login, APIs, landing pages) with reliable DOWN/RECOVERED notifications.
• Automation engineers needing n8n URL uptime monitoring with response-time tracking and incident history.
• Operations teams generating daily uptime + latency insights without manual reporting.

Technical details

• Nodes/logic: Schedule Trigger, if, Code, Data Table, Email Send, Sticky Note.
• Data Tables: url_checks (url, ok, status_code, response_ms, reason, checked_at) and url_incidents (status, reason, …).