Get alerted when a Make scenario stops running
Make tells you about some errors. A heartbeat tells you about the silence.
How Make scenarios go quiet
- Automatic deactivation after consecutive errors.
- Out of operations for the month on your Make plan.
- Expired connections to Google, Microsoft, or other OAuth apps.
- Successful runs with no bundles — a search that returns nothing, a filter that drops everything.
Add a heartbeat module
Finish the scenario with HTTP → Make a request, POSTing to your Did It Run? ping URL with an item count. Create a watch with the scenario's schedule and a grace window. If the request doesn't arrive by the deadline, you're alerted by email, Slack, Discord or Telegram — and again when it recovers.
Use an error handler for instant failure alerts
Add an error handler route that calls /fail on the same URL, so failures alert immediately instead of at the deadline.
Agencies: one roll-call per morning
Put each client's scenarios in a client folder (Pro) and read one roll-call email listing every scenario that ran, missed, or came back empty.
FAQ
Does the HTTP module cost operations?
Yes, one operation per run. Email check-ins (which would let you use the Email module instead) are coming soon; for now the HTTP module is the way to check in.
What schedule should I use for instant (webhook) scenarios?
Use the longest normal quiet period, e.g. at least once a day, so you hear about it when incoming events stop.
Know the next time it doesn't run
Know when your AI agents and automations didn't run. Free for 3 watches.
Start free