It’s appalling how many big companies spend more on advertising than on improving security (2FA Directory is a great resource).
It’s a lot easier than it appears. Healthchecks offers a lot of flexibility so it’s like a multitool where half the widgets you’ve never seen before, at the end of the day you really only need to figure out how to use one or two of them.
With Healthchecks, you’re either pushing or pulling a small amount of data. The hardest part is deciding which method to use because Healthchecks supports so many options.
In the push/pull examples I shared earlier, I use cURL for the web requests because it’s been around for long enough to be ported to Linux, macOS, Windows, DOS, Android, iOS and at least 20 other platforms.
cURL also supports SMTP, so msmtp and Apprise aren’t necessary if all that’s needed is email notifications.
The funny thing is that sending email via SMTP is actually incredibly easy (it can be done in seconds with just telnet).
Desktop and web-based email interfaces such as Mozilla Thunderbird, Microsoft Outlook, Gmail, Yahoo Mail, etc. make it point-and-click easy, but the flip side is that automation isn’t so easy.
The example I gave earlier pipes the output from STC to Apprise for emailing:
stc | apprise 'mailto://examplemailserver.com?from=me@example.com&to=you@example.com'
Not only is it straight forward, it works as-is on the command-line on Linux, macOS and Windows, and it can also be used as-is in a variety of launcher apps. A program with a GUI often gets in the way of automation.
Now that is actually more complicated than it sounds. 
Assuming it’s a mesh VPN, or otherwise all of the devices are visible to each other on a private LAN, then the first tool that comes to mind is netcat.
Also of course, if any devices have a host-based firewall, the necessary adjustments will need to be made.
Healthchecks doesn’t actually monitor cron jobs. Instead, cron jobs are used to automate contacting Healthchecks on a schedule.
In Un*x, cron jobs are the counterpart to Windows Task Scheduler on Windows and Launcher on macOS.
Although you might not have any cron jobs for your user account on your PCs, a typical Linux system has a dozen or more that handle various scheduled tasks including updating a software catalog, clearing temp files, rotating logs, etc.
Although it’s easy to create a crontab by hand, there are plenty of GUI tools available. A couple of pointers:
That’s where cron fits in. 
In the following example crontab, the output from stc is piped to apprise for emailing at 15-minute intervals (relative to midnight):
*/15 * * * * stc | apprise 'mailto://examplemailserver.com?from=me@example.com&to=you@example.com'
There’s no error checking so it’ll send emails 4 times per hour, all day long, and every day until the cron job is stopped. If you turn off your laptop, it’ll fire at the next scheduled time.
Fortunately there are a lot of great resources online. In keeping with the analogy, break it up into bite size pieces, go snack size first, then follow with an entire meal. 
Un*x/Linux tools tend to be small and single purpose rather than kitchen sink apps. It’s like combining Lego pieces to build any contraption one can think of.
).