n8n Website Uptime & Latency Monitoring with Slack Alerts

Keep your websites fast—and your team instantly informed

This n8n workflow runs scheduled HTTPS uptime and latency checks for your configured list of websites, stores monitoring history in n8n Data Tables, and sends deduplicated incident + recovery alerts to Slack, including a daily summary.

What this workflow does

• Runs on two schedules: one for periodic uptime/latency checks and another for the daily summary.
• Loads monitor configuration, initializes the required n8n Data Tables, and validates enabled monitors (ensuring safe HTTPS URLs and sane threshold settings).
• Checks each enabled monitor by performing an HTTP request and normalizing results into healthy, slow, or failed outcomes (including status code, latency, and error details).
• Persists every check to a check-history table, then compares the result to the prior saved monitor state to detect:
  • Outages (failed conditions)
  • Latency degradation (slow conditions)
  • Recoveries (when conditions return to normal)
• Upserts monitor state + incident details into Data Tables and uses deterministic notification keys to prevent duplicate Slack alerts.
• Sends only eligible alerts to Slack, records the notification outcome in a ledger, and on the daily run calculates uptime/latency statistics from stored history, posts a Slack summary, and applies retention-based cleanup.

Use cases

• Monitor critical customer-facing endpoints and detect downtime or performance degradation automatically.
• Provide SaaS ops teams with daily uptime/latency reporting directly in Slack.
• Reduce alert noise by sending deduplicated incident and recovery notifications.

Technical details

• Slack integration via Slack OAuth2 credential and configurable Slack channel ID (alerts + daily summary).
• Uses n8n nodes including: if, set, code, merge, slack, and switch.
• Stores monitoring state, check history, and notification ledger in n8n Data Tables with retention controls.

Setup (quick start)

• Connect a Slack OAuth2 credential.
• Set the target Slack channel ID for both the alert and daily summary Slack nodes.
• Update the workflow configuration with your monitors (enabled HTTPS targets and threshold values).