Zapier Catch Hook test trigger with Sume Send test
Zapier lists the three most recent webhooks from the past hour. Use Sume's Send test to put a signed webhook.test sample there before a real run exists.
Point your Sume webhook at the Zapier Catch Hook URL and use Send test, which fires a dummy signed webhook.test payload, so the trigger has a sample to map before any real run finishes. Zapier's page says webhook triggers show the three most recent webhooks sent to the URL within the past hour.
Sume behavior is from the Run webhooks docs; the Zapier text was read 2026-09-30.
What does Send test send?
Send test lives on /dashboard/webhooks and as POST /v1/webhooks/test-deliveries with account:write. It is a dummy webhook.test payload, not a replay of a real Format run, and its request_id starts with req_wh_test_. It has no job_id and no arun_ id.
| Source | Payload | Real run needed |
|---|---|---|
| Send test | Dummy webhook.test | No |
| Redeliver a run | Current format.run.terminal receipt | Yes, a terminal run |
| Wait for a real event | The actual terminal payload | Yes |
Why not map fields from the test sample?
The sample carries no real run fields, so a Zap mapped from it may miss the ones your live events have. After mapping, redeliver a real terminal run to refresh the sample: POST /v1/format-runs/{run_id}/webhook/redeliver with formats:write re-posts the current receipt with a fresh timestamp and signature.
curl -X POST https://api.sume.com/v1/format-runs/arun_demo/webhook/redeliver \
-H "Authorization: Bearer $SUME_API_KEY"Does the Zap need to verify the signature?
Sume signs every delivery, and the docs describe checking it in your own code with verifyWebhook; they do not describe a check on the Zapier side. If the Zap acts on money or data, verify in a small relay you control before forwarding, and route on event so webhook.test does not trigger a real action.
What if the sample has expired?
Zapier keeps only recent requests, so send another test or redeliver rather than waiting. Redeliver does not consume one of the 10 automatic attempts.
Sources
Related posts
More in Developers
- Will a 100-item Sume bulk run hit Zapier's webhook rate limit?
A Sume bulk queue holds up to 100 items, each with its own webhook. Compare that with Zapier's per-Zap webhook limit and know what Sume does on a 429.
- Zapier accepted my Sume webhook but the Zap ran minutes later
Zapier says it may return 200 and delay webhook processing by minutes. Sume sees a delivered 200, so keep a status poll as the backup for run and job results.
- Captions misspell your brand name: fix it with authored cues
Sume video captions have no custom dictionary field. Pass cues with your own spelling and speech-to-text is skipped, so the brand name prints as written.
- AI music exactly 30 seconds: no duration field, use Timeline
Music Router rejects duration and duration_seconds. Ask for the length in the prompt, then fix the exact output length with Timeline 1.0 audio.duration_seconds.
Written by Sume