Zapier Catch Hook URL is the same in test and live: test Sume safely

Zapier's help page says the Catch Hook URL is the same in test and live, so there is no separate test address to keep real traffic away from. For Sume, that means the safest first check is a test delivery: POST /v1/webhooks/test-deliveries sends a dummy, signed webhook.test payload to a URL you type, and it is explicitly not a job or Format run. Use it to see the shape in the Zap before any real result arrives.

What the two sides say

From Zapier: a Catch Hook accepts up to a 10 MB trigger payload (2 MB for Catch Raw Hook), answers 200 when the Zap is active, and answers 404 when the Zap is disabled or deleted, which can take up to several hours to take effect. From Sume: a delivery needs a 2xx within 10 seconds, and any other answer, including a 3xx, is a failed attempt.

Steps

Run these in order, once, before the campaign.

• Create the Zap with a Catch Hook trigger and copy its address.
• Call the test route with that URL, then use Zapier's test trigger to pick up the sample.
• Map the fields you need from the real shape later, since the test body has only ok and a message.
• Turn the Zap on, then start one real run and confirm the terminal event arrives with the run id as request_id.

What Sume does not do

The test delivery proves your URL answers and your verifier works. It does not prove that your field mapping matches a real receipt, because the test payload is a dummy. Sume also does not tell you the Zap is off; it only sees the 404, counts a failed attempt, and retries.

If a Zap was off during a run, the run is unchanged and you can ask for the delivery again with the redeliver endpoint after you turn it on.

Why this matters in a sale week

Because the address is shared, a test you run on Black Friday morning goes to the same place as live traffic. Keep a naming habit in the Zap, such as a filter step that ignores any event named webhook.test, so a test never triggers a paid downstream action like sending a customer email. The Sume event name is in the body, so the filter is a one-line condition.

Also remember that Zapier says disabling or deleting a Zap can take up to several hours to take effect. If you switch the Zap off to stop a flood, expect a window in which the old behavior continues, and expect Sume to keep retrying afterwards if the replies turn into errors.