Guide · No-code
Monitor Make (formerly Integromat) with a dead man's switch
A Make scenario can stop running without any red flag: a trigger gets deactivated, an app connection expires, an operations quota is hit. A Mortemain check-in catches all of it, because it alerts on silence, not just on a scenario error.
1. Create a check
Create a check in Mortemain with the same schedule as your scenario's trigger (interval, webhook, or app trigger), and a grace window wide enough for normal run-time variance. Copy its ping URL:
https://ping.mortemain.com/your-check-uuid
2. Add an HTTP module at the end of the scenario
At the very end of your scenario, add an HTTP → Make a request module. Set the method to GET and the URL to your ping URL:
Method: GET URL: https://ping.mortemain.com/your-check-uuid
Because it's the last module in the flow, it only runs once every preceding module has completed successfully, so a check-in genuinely means the whole scenario finished, not just that it started.
3. Alert immediately on failure
Right-click the module most likely to fail (or wrap the whole route) and choose Add error handler. Inside the handler, add another HTTP → Make a request module pointed at the /fail URL:
Method: GET URL: https://ping.mortemain.com/your-check-uuid/fail
Set the handler to Resume or Ignore so the scenario doesn't retry into a loop. The /fail ping alerts you the moment something breaks, instead of waiting for the next scheduled run to go missing.
4. Track scenario duration (optional)
To see how long each run takes, add a first HTTP module that pings /start before any real work happens:
Method: GET URL: https://ping.mortemain.com/your-check-uuid/start
Mortemain then shows the elapsed time between the /start ping and the final check-in, so a scenario that suddenly runs long (a slow API, a growing dataset) shows up without a separate alert rule.
Test it
Run the scenario once manually and confirm the check flips to up in Mortemain within a few seconds. Force an error (disable a connection, or trigger the error handler with a test run) to confirm the /fail ping arrives immediately, then deactivate the scenario for one cycle to confirm the missed-check-in alert fires after the grace window, that's the failure mode Make's own notifications won't catch on their own.
No HTTP module available on a given step? The general webhook / "call a URL" guide covers the same pattern for Zapier, Power Automate, n8n, and plain webhook fields.