HTTP Endpoint Monitoring Workflow: Slack & Sheets Alerts

Keep every critical HTTP endpoint under watch—alert only when it matters

This HTTP Endpoint Monitoring n8n workflow checks your endpoints every 5 minutes, verifies health, and sends Slack alerts only when a service goes down or recovers. It also logs events to Google Sheets (optional) and posts a daily Slack digest for anything still down.

What this workflow does

• Schedules monitoring to run every 5 minutes (or you can run it manually).
• Loads a predefined endpoint list containing name, URL, and an optional expected health field.
• Requests each endpoint over HTTP using a 15-second timeout, capturing the full response without failing the whole workflow on errors.
• Evaluates health using the HTTP status code, and—when configured—validates a specific response body field matches the expected healthy value.
• If an endpoint looks unhealthy, it waits 30 seconds and retries once to confirm the outage.
• Tracks last-known state per endpoint, including how long it has been down and consecutive failure counts.
• Posts to Slack only on state changes: one alert when an endpoint goes down, and another when it recovers.
• Escalates to Slack after 6 consecutive failed checks for an endpoint.
• At 08:00 daily, sends a Slack digest only if any endpoints are currently still down (and nothing if everything is healthy).

Use cases

• Monitor APIs and web services (REST endpoints) used by your SaaS or internal systems.
• Detect “silent failures” via optional expected health fields in responses—not just status codes.
• Reduce alert fatigue by sending Slack messages only when an endpoint changes state.
• Provide operators with a daily “still down” summary without checking dashboards manually.

Technical details

• n8n workflow nodes: if, set, code, no op, wait, slack
• Slack integration for outage, recovery, escalation (6 failures), and daily 08:00 digest
• Google Sheets logging (optional) when an endpoint goes down/reports events

Setup: Update the endpoint list (name, URL, optional expected health field), add Slack credentials, and configure the target channel(s).