I built this after the third time an automation stopped running and I found out from an angry customer rather than from any alert. The distinction that matters: platforms alert on errors. A workflow that quietly stops firing throws nothing, so there is no error to catch, and it looks identical to a quiet week until someone downstream asks where their data is. So the whole product is one HTTP endpoint and an inbox. You get a URL, your workflow requests it when it finishes, and if a request does not arrive within the schedule plus a grace period you get an email. When pings resume you get one all clear. No AI, no OAuth, no access to your workflow data, nothing to install. The part I spent most of the time on is the part nobody sees. One outage produces exactly one email, enforced at the database with a conditional write so two concurrent checkers cannot both send. Daily schedules are evaluated in your timezone, and a wall clock landing in a spring forward gap resolves forward, because resolving backward would pull a deadline an hour early and cause exactly the false alarm this exists to prevent. Grace defaults to twice your interval, because a monitoring tool that cries wolf on day one gets muted and then it is worse than nothing. healthchecks.io does the generic version of this well and is open source, so if you want to self host, genuinely use that. This is narrower: built around n8n, Make and Zapier, with setup guidance in each platform's own terms. There is a free webhook tester at silentfailapp.com/webhook-tester if you just want to confirm your HTTP node fires at all. No signup, no account. Free tier is 3 monitors. Happy to answer anything.

Silent Fail

Get an email when your automation stops running

Get an email when your automation stops running