n8n Monitor API Health & Slack Alerts on Status Change

Automatically monitor your API health and alert your team in Slack only when it changes

This n8n workflow checks a configured API health endpoint every 30 minutes and sends a Slack notification only when the health status flips—posting “DOWN” when the service becomes unhealthy and “RECOVERED” when it returns to normal.

What this workflow does

• Runs on a schedule: uses a Schedule Trigger to execute every 30 minutes.
• Performs a health check safely: calls your health endpoint using n8n’s HTTP Request (with Never Error) so timeouts or 5xx responses are captured as data rather than failing the whole workflow.
• Validates the response: includes a custom validation step (via a code step) to determine whether the service is up—for example, checking criteria like ok === true.
• Debounces repeated alerts: compares the current health verdict against the last stored verdict and sends a message only when the status changes.
• Notifies in Slack: posts a timestamped “DOWN” or “RECOVERED” message to your selected Slack channel.

Use cases

• SaaS operators who need reliable API uptime visibility without alert spam.
• Automation engineers who want a simple n8n API monitoring workflow with change-based Slack alerts.
• Teams managing external dependencies who want immediate awareness when a downstream API becomes unhealthy.

Technical details

• Nodes/steps: Schedule Trigger, HTTP Request, Code (validation + status comparison), Slack, Sticky Note.
• Slack integration: sends “DOWN”/“RECOVERED” messages to a chosen channel.
• Setup: update the HTTP Request URL to your health endpoint, adjust the success criteria in the code step to match your payload, and configure Slack credentials/channel.

Result: lightweight n8n API health monitoring with Slack notifications triggered by status change—not repeated checks.