Docs › Zapier Zap monitoring with RunVouch
Zapier Zap monitoring with RunVouch
Zapier Zap monitoring beyond Zap History: a Zap with a Schedule by Zapier trigger runs until Zapier turns it off (repeated errors, a disconnected app, a plan limit). Zap History shows what happened; it does not call you.
How it runs on Zapier
Two Webhooks by Zapier steps (POST, JSON), one right after the trigger and one at the end.
Store the key
Paste the key in the header field of both webhook steps, or keep it in a Storage by Zapier value.
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":"weekly-digest","source":"zapier"}'
# -> {"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 Zapier
- Zapier turning a Zap off, and held tasks when a plan limit is reached, are both silent until you open Zap History.
- Filter steps that stop a run early are successful runs; only the end call with evidence distinguishes them.
What Zapier does not tell you
Zapier e-mails you when it turns a Zap off after a high error ratio and when a connected account needs re-authorizing; both are single e-mails to the account owner. Held tasks (plan limit reached) and a Zap paused by a teammate are only visible in Zap History and the Zap list. A run stopped by a Filter step counts as a successful run with the label Filtered.
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?
Home Assistant automations. n8n (community node). Make (Integromat). 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