I had an automation running every night to back up client files. Last week someone asked me for an old record, and when I went to find it — nothing. Three days of backups had simply never run. Turns out a tool upgrade had quietly reset my config. Three days of data, just gone.
The scary part isn't that the task failed. It's that I had no idea it had failed. No error. No alert. Everything looked normal — right up until the moment I actually needed the data.
That's when I finally learned there's a specific name for this kind of solution: "heartbeat monitoring."
What Healthchecks.io is — and how people are already using it
The concept is simple: you give each automated task a "check -in point." Every time the task finishes, it sends a tiny signal to that endpoint — like clocking in. If it goes too long without clocking in, the service emails or messages you.
Healthchecks.io is a dedicated tool for exactly this. It's been running for several years, and they've recently moved to self-managed storage, which has made it even more reliable .
Xiaolin, a freelance designer in Guangzhou, runs a script every Monday morning that compiles her weekly client orders and sends the summary to her inbox. Before, she had no way of knowing if it had actually run. After she set up Healthchecks.io, one Monday the summary didn't arrive — and she got an alert the same morning. Turned out a config issue had broken the script. She fixed it that day, and her bookkeeping stayed on track.
If you're running scheduled tasks through Zapier, Make, Feishu automation, or even iOS Shortcuts, you can wire any of them into this kind of monitoring.
What it actually costs to set this up today
- Money: The free tier supports up to 20 monitored tasks — plenty for solo use. Paid plans start at $20/month for teams.
- Time: Sign up and configure your first monitor in about 10 minutes.
- Technical barrier: No coding required. Your automation tool just needs to be able to "visit a URL" — Zapier , Make, and Feishu automation can all do this. The setup is literally: add one final step to your workflow that hits a link.
- First step: Go to healthchecks.io, click "Sign Up" in the top right, then click "Add Check." Give the task a name, set how long a missed check-in should wait before triggering an alert, copy the generated URL, and paste it as the last step in your automation. Done.
I messed this up the first time — I set the time unit to "minutes" instead of "hours" and spent a while getting flooded with false alerts before I figured out what happened. You know the trap now. Don't fall in.
What I'd suggest depending on where you are
If you're just starting out and don't have any automated tasks yet : You don't need this tool right now. Set it up when your first automation is actually running — no need to borrow stress from the future.
If you have one or two clients and you've started using Zapier or Feishu automation to handle repetitive work: I'd at least put your most important task on monitoring. When something goes wrong on a client deliverable, knowing within the hour versus knowing three days later is a very different situation. Ten minutes is worth it.
If you're scaling up, have someone handling ops, and are running multiple automation flows: The free tier's 20 monitors may not be enough. Consider the paid plan, or look into their open-source version for self-hosting (you'll need someone comfortable with basic server work). The goal is to stop "did it actually run?" from being something a human has to manually check.
This tool isn't for everyone. If everything you do is still manual, skip it for now. But if you've already started letting machines do work for you, it's worth spending 10 minutes letting another machine keep an eye on them.