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
Workflow Pings watches workflows you already run in n8n, Make, and Zapier. The workflow pings a private link when it finishes. If the pings stop, or the workflow calls the failure link, Radar My Business emails you.
Starter watches 5 workflows, Pro 25, Agency 100. Included in the same subscription, not a separate one. 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.
Catch runs that finish but do nothing
The success ping can also carry what the run did. Send count with the number of items processed, and snippet with up to 1,000 characters of an API response. A count of 0, or a message or snippet with words like unauthorized, forbidden, invalid token, expired, rate limit or error, counts as down: one email, then one recovery email after a clean run. On every plan, you can also set your own minimum item count and extra words on the monitor.
POST https://radarmybusiness.com/api/agent-monitor/ping/<your-token>
{"count": 42, "snippet": "200 OK, 42 rows synced"}
GET https://radarmybusiness.com/api/agent-monitor/ping/<your-token>?count=0A 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. Working means the last success was on time. Running late means it is overdue and still inside the grace period. Stopped means the grace passed or a failure ping arrived.
See plans · Set up with n8n · Set up with Zapier · Set up with Make · Compare with Healthchecks.io
Example report · rvrentalswayoflife.com
Workflow Pings: are the automations still running?
Each workflow pings Radar when it runs. If one reports a failure or goes quiet, RV Rentals Way of Life gets one email, and another when it recovers.
Example report. Sample data for illustration; not real results for this business.
- Automation - Recovered ✓New booking → cleaning schedule (n8n)Last ping Today 7:02 AM · Recovered after 1 missed run
- Automation - FailedWebsite lead form → CRM (Zapier)Last ping Today 9:15 AM · Reported a failure: CRM login expired
- Automation - QuietNightly review request texts (Make)Last ping Yesterday 8:00 PM · No ping in 26 hours (expected daily)
- OKDelivery route sheet (n8n)Last ping Today 6:30 AM · On schedule
No card needed. Nothing is charged when the trial ends.