Step 01
Add the workflow
Name it, pick n8n, Make, or Zapier, and say how often it should run. Add a grace period so a few late minutes do not count as an outage.
Radar My Business
Know when an automation stops, before a client does
Agent Monitor watches workflows you already run in n8n, Make, and Zapier. The workflow calls a private link when it finishes. If that link goes quiet, or the workflow calls the failure link, Radar My Business emails you.
Included with Starter, Pro, and Agency. Not a separate subscription. Hello@RadarMyBusiness.com
How a ping works
Step 02
Call the ping link
Each monitor has a private success link and a failure link. Put the success link at the end of the workflow. Point a failure path at the failure link.
Step 03
Get one email
If the success link goes quiet past the grace period, or the failure link is called, you get one email. When the workflow pings success again, you get one recovery email. Not a message every hour.
What you put in the workflow
No code. Copy the link from the monitor and paste it into the tool you already use. GET and POST both count.
n8n
Add an HTTP Request node at the end. Method POST, URL is the success ping. On the error workflow, POST the failure link.
Make
Add the HTTP “Make a request” module. URL is the success ping. On the error handler, call the failure link.
Zapier
Add Webhooks by Zapier, POST, and paste the success ping. Use the failure link on a path that only runs when something failed.
A public n8n instance can also be checked from its execution history once a day. That is optional. The ping link is the method that works for n8n, Make, and Zapier. Up means the last success was on time. Late means it is overdue and still inside the grace period. Down means the grace passed or a failure ping arrived.