Monitor Multiple API Endpoints and Alert on the First Failure
An n8n workflow that pings a list of critical URLs every few minutes, checks status code and response time, and alerts Slack the moment one fails or slows down — a free, self-hosted uptime monitor for the endpoints a single-URL checker would miss.
- 1
Schedule frequent checks
A
Schedule Triggerevery 5 minutes starts the run. ASetnode holds your list of URLs to monitor. - 2
Ping each endpoint
An
Item Listssplit plus anHTTP Request(withneverErrorand a timeout) hits each URL, capturing status code and response time. - 3
Detect state changes
A
Codenode compares each result to the last stored state; it flags only endpoints that just went down or just recovered, then saves the new state. - 4
Alert on change
An
IFkeeps only changed endpoints and aSlacknode posts a clear up/down message with the URL, status and latency — so you hear about problems before customers do.
Frequently asked questions
How is this different from a single website-down check?
It monitors many endpoints in one run — your homepage, checkout, login API, webhook receiver — because outages often hit one service while the homepage stays up. You define the URL list once and every one is checked each cycle.
Does it spam alerts while something stays down?
It stores each endpoint's last state in workflow static data and only alerts on a state change (up→down or down→up). So you get one 'down' alert and one 'recovered' alert, not a message every 5 minutes.
Verify Your Nightly Backups Actually Succeeded and Alert If Not
An n8n workflow that each morning checks whether last night's backup ran, is recent enough, and is a sane size — then alerts you loudly if anything is off, so you discover a broken backup on a quiet Tuesday, not during a real disaster recovery.
Free recipe
Escalate GitHub Security Alerts to PagerDuty Instantly
An n8n workflow that catches GitHub Dependabot and code-scanning security alerts, filters for high and critical severity, and opens a PagerDuty incident with the vulnerability details — so a serious CVE in your dependencies wakes the on-call engineer instead of sitting unseen in the Security tab.
Free recipe
Turn a New GitHub Release into a Plain-English Changelog Announcement
An n8n workflow that fires when you publish a GitHub release, has Claude rewrite the raw release notes into a friendly, user-facing changelog, and posts it to Slack and a Discord community channel — so shipping a version instantly tells your users what's new, in words they understand.