Docs › Zapier Zaps with RunVouch

Zapier Zaps with RunVouch

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 RunVouch detects

Need a key? Get a free key · Stuck? contact