Monitor Make.com scenarios

Use WatchCat's cron ping URLs to verify that your Make.com automation scenarios run on schedule.

Make.com scenarios run on a schedule, but they fail silently. If a scenario is accidentally turned off, hits an error, or gets stuck on an API rate limit, you won't know until you check manually — or until a customer reports a problem.

Adding a WatchCat ping as the last module in a scenario takes under a minute and gives you an alert if the scenario misses a run.

Step 1 — create a cron monitor

In WatchCat, go to Cron monitors → New monitor. Set the schedule to match your scenario's frequency. Add a grace period of a few minutes to account for Make.com's scheduler not firing at the exact second.

Copy the ping URL from the monitor detail page — you'll paste it into Make.com next.

Step 2 — add an HTTP module to your scenario

Open your scenario in Make.com and add an HTTP → Make a request module at the very end of the flow — after all other modules have completed.

URL https://watchcat.io/p/cron/YOUR_TOKEN

Method GET

Parse response Off — you don't need the response body

Save the scenario. The next time it runs, Make.com will ping WatchCat at the end of each successful execution.

Track start and end for long scenarios

If your scenario takes several minutes to complete, add a second HTTP module at the beginning of the flow that pings the /start endpoint, and change the final module to ping /end:

First module URL https://watchcat.io/p/cron/YOUR_TOKEN/start

Last module URL https://watchcat.io/p/cron/YOUR_TOKEN/end

If the scenario starts but the final module never fires — because of an error mid-flow — WatchCat will open an incident once the expected run window passes.

Common causes of missed pings

Scenario is turned off — Make.com won't run scheduled scenarios that are inactive
Error in an earlier module — if a module before the ping fails, Make.com stops and the ping never fires
API rate limit or timeout in a third-party service — scenario pauses mid-run
Make.com scheduled maintenance or outage

Tip: Place the ping module after error handlers if you use them, so that the ping only fires when the scenario genuinely completes its work — not just when it finishes handling an error gracefully.

Recommended settings

Schedule Match your scenario's run interval exactly

Grace period 5–10 min — Make.com rarely fires at the exact scheduled second

Alert after 1 missed run for critical automations

Start monitoring in minutes

Free plan available. No credit card required.

Start free See pricing View subprocessors