ZapBounce

ZapBounce and Zapier

Zapier charges per task, and a webhook call is a task. That makes the cost model here different from every other integration on this site: the verification credit is the cheap part.

Design accordingly. A Zap that verifies one address per trigger is fine at form-submission volume and expensive at list-processing volume.

Per-task pricing punishes row-by-row verification

Running a thousand addresses through a Zap one at a time costs a thousand tasks, plus whatever the steps after the verification cost. At list scale that exceeds the verification spend several times over.

The right shape for a list is to submit a batch from one task and let the webhook come back to a second Zap, which is two tasks rather than two thousand.

For genuine real-time work, a form submission or a new CRM record, one task per address is exactly right and the cost is negligible.

How the data moves

  1. Use Webhooks by Zapier for the call

    A POST action with the key in a header and the address in the body. No custom app needed.

  2. Add a Filter step on the verdict

    Steps after a filter do not consume tasks when the filter stops the Zap, so filtering early is both correct and cheaper.

  3. Batch anything list-shaped

    One task submits the batch, a catch hook receives the completion event, and a second Zap handles the results.

  4. Use a Storage or Lookup step to avoid re-checking

    A Zap that re-verifies the same address on every CRM update is spending tasks and credits on a question already answered.

Setting it up

  1. Add a Webhooks by Zapier POST step pointing at the verify endpoint.
  2. Put the key in an Authorization header, never in the URL.
  3. Map the trigger's email field into the JSON body.
  4. Add a Filter step that continues only when the verdict is valid.
  5. For list work, use a separate Zap with a catch hook to receive batch completion events.
  6. Add error handling so a failed verification does not silently stop the Zap.

Zapier: common questions

Does verification cost a Zapier task?

Yes, one per webhook call. For a list, submit a batch from one task instead of looping.

Where does the API key go?

An Authorization header in the webhook step. Never the URL, which ends up in logs.

Should the filter continue on catch-all?

Depends what comes next. For a sending step, no. For a CRM update that records the verdict, yes.

Reference

Check a Zapier export today

100 free checks a month, no card. Unknown results and duplicates are never billed.

Get an API keySee pricing