Guide
Monitoring Make scenarios without pretending Make has a useful public API.
Most agencies run a mix. The n8n instance is easy to poll. The Make scenario that texts a lead in under a minute is not. Heartbeats cover that gap.
Add one HTTP module at the end
Create a heartbeat in LeadPulse, copy the URL, and add an HTTP module as the last step of the Make scenario. Method GET or POST. If the scenario knows how many bundles it processed, pass count as a query parameter.
Set the interval a little wider than the scenario’s schedule. A scenario that should run every 15 minutes can use a 30-minute heartbeat so a single slow queue does not page you. A scenario that should fire on every lead can use a tighter window during business hours — start with the longest gap you are willing to explain to the client.
What you will be told
If Make is paused, the HTTP module never runs, and the heartbeat goes overdue. If Make runs and the iterator was empty, you can pass count=0 and get a different alert: it ran, and it delivered nothing.
Zapier works the same way. So does a custom agent, a cron on a VPS, or a Cloudflare Worker. The checker does not care which product called the URL.
Put it on the client report
Heartbeats belong to a client, same as workflows. The weekly report’s incident list includes missed heartbeats, so the Monday email covers the Make scenario and the n8n workflows in one place.