Docs › Make scenario monitoring with RunVouch
Make scenario monitoring with RunVouch
Make scenario monitoring after the deactivation e-mail: a Make scenario on a schedule runs until Make deactivates it after consecutive errors, or until someone toggles it off. The deactivation e-mail is easy to miss, and a scenario that runs with zero bundles is a normal run.
How it runs on Make (Integromat)
Two HTTP modules in the scenario: one at the start, one at the end, with the API's JSON.
Store the key
Store the key in a Make connection or as a scenario variable; put it in the X-API-Key header of both HTTP modules.
Report the run (two HTTP calls)
# 1. at the start of the job
curl -s -X POST https://api.runvouch.com/v1/runs/start -H "X-API-Key: $RUNVOUCH_KEY" \
-H "content-type: application/json" -d '{"agent":"lead-enricher","source":"make"}'
# -> {"run_id":"..."}
# 2. at the end, with what you know: status, cost, evidence
curl -s -X POST https://api.runvouch.com/v1/runs/end -H "X-API-Key: $RUNVOUCH_KEY" \
-H "content-type: application/json" \
-d '{"run_id":"...","status":"ok","cost":0.12,"evidence":{"rows_written":true}}'The start call returns run_id; the end call takes status (ok or fail), optional cost and tokens, and evidence as a JSON object of booleans. Full reference on the API page.
Register the cadence and caps
rv agent nightly-report --cadence 24h --grace 30m --max-runtime 1h --evidence --cap-run-cost 2
Register the agent once, from anywhere with the key. Cadence is what turns a schedule that stopped into an alert; --evidence makes a run without evidence a failure; the caps pause the agent when it overspends.
What goes silent on Make (Integromat)
- Auto-deactivation after errors is documented Make behaviour; the scenario does not run again until you re-enable it. MISSED tells you the same hour.
- Zero bundles processed is a successful run in the history; report
evidence: {"bundles": count > 0}from the end module. - Operations consumed by an OpenAI module are visible per run in Make; passing the cost into the end call makes the daily cap work.
What Make (Integromat) does not tell you
Make sends one e-mail when it deactivates a scenario after consecutive errors and shows warnings in the scenario list; it does not repeat the warning, and it sends nothing for a scenario someone switched off. Scenario history keeps each execution with its operations count; an execution that processed zero bundles is a successful execution with a small number.
What RunVouch detects
| Alert | What it means here |
|---|---|
| MISSED | cadence plus grace passed and no run started |
| FAILED | non-zero exit or a reported failure, with the stderr excerpt |
| NO_EVIDENCE | the run said ok but the file, URL or assertion you required is missing |
| STALLED | a run started and never ended within max runtime |
| RETRY_STORM | the same tool called with identical input many times in one run |
| BUDGET_RUN / BUDGET_DAY | cost cap crossed; the agent is paused until you resume it |
| DRIFT | duration or output size far off its 7-run baseline |
Set up in two minutes
- Get a free key (3 agents, no card) and store it where this page says.
- report the run (two http calls): copy the snippet above into the scheduled job.
- Register the cadence once:
rv agent nightly-report --cadence 24h --grace 30m --evidence, or let the first run create the agent and set the cadence on the dashboard. - Send one test alert:
curl -X POST https://api.runvouch.com/v1/settings/test-alert -H "X-API-Key: $RUNVOUCH_KEY". The next missed, failed or empty run reaches the same channels.
Also running no-code automation?
Zapier. Home Assistant automations. n8n (community node). The full list of runtimes is on integrations, and the same agent can report from several of them: one job, one cadence, wherever it happens to run.
Need a key? Get a free key · Stuck? contact