Website Uptime Monitor: HTTP Check + ntfy Outage Alerts

Keep your websites online: HTTP uptime checks with instant ntfy outage alerts

This n8n workflow monitors a target website every five minutes using an HTTP request. When the returned HTTP status code doesn’t match your expected value, it immediately sends a high-priority downtime notification to an ntfy topic—so you can detect outages fast.

What this workflow does

• Runs on a schedule: executes every five minutes to perform an uptime check.
• Loads monitoring settings: reads the target URL, the expected HTTP status code, and your ntfy server/topic configuration.
• Performs an HTTP check: requests the target URL and captures the full HTTP response without failing on non-2xx status codes.
• Compares status codes: compares the returned status code against the expected value and adds a timestamp for the check.
• Alerts only on failure: if the check fails, it posts a formatted alert message to the configured ntfy topic; otherwise it ends without sending a notification.

Use cases

• Website uptime monitoring: alert when your landing page, API endpoint, or app health endpoint returns an unexpected status.
• SaaS operational visibility: detect regressions where an endpoint starts returning wrong status codes (e.g., 200 expected but 500 returned).
• Lightweight incident notifications: use ntfy for fast, high-priority outage messaging without configuring a full monitoring stack.

Technical details

• Schedule Trigger: runs every five minutes.
• HTTP Request: checks the target URL and captures the HTTP response even for non-2xx results.
• Comparison logic: uses if to decide whether the returned status code matches the expected value.
• Configuration & formatting: set, code, and sticky note components to manage inputs and create the alert payload.
• Outage alerts via ntfy: posts the downtime notification to your private ntfy topic (authentication can be configured in the relevant HTTP request settings if required).

Setup summary

Provide the target URL and expected status code, choose your ntfy server and private topic, run a test execution, and activate the workflow. Adjust the schedule interval if needed.