ZapBounce

ZapBounce and Zapier

Yes, you can check new leads automatically in Zapier. Add a Webhooks by Zapier step that calls ZapBounce's verify endpoint, map the email field, and the next step gets a status of valid, invalid, catch_all or unknown, plus role and disposable flags. A filter step then decides what continues.

The same check works outside Zapier. Make and n8n call the ZapBounce API through their HTTP modules, and a polled job reports when a big list is done. The routes differ, but the result format is the same everywhere.

Zapier bills tasks, so the Zap's shape sets the cost

Zapier charges per task, and each action step that runs is a task. At form-submission volume, one check per new lead costs almost nothing in tasks, and it's exactly the right design.

A list is different. Looping a thousand addresses through a Zap one at a time costs a thousand tasks plus whatever runs after the check, which can outweigh the $5 the checks themselves cost.

For a list, submit one job from a single task and let a scheduled second Zap poll for completion. That's two tasks instead of two thousand, and the results arrive as one file.

How the data moves

  1. Add a webhook step for the verify call

    Send a POST to /v1/verify with your API key in an X-API-Key header, after any trigger: a form entry, a new CRM contact, a new row in a sheet. The response carries every field from the result codes page.

  2. Filter on the result early

    Zapier doesn't charge for steps a filter stops, so filtering right after the check is both correct and cheaper. Continue on valid for a sending step.

  3. Give catch_all its own path

    A catch_all result describes the domain, not the person. Use Paths to send those leads to a CRM field or a slower sequence rather than dropping real customers.

  4. Poll for job results

    For list jobs, a scheduled Zap calls GET /v1/jobs/{id} and, once the job completes, pulls the results page by page into your destination app.

Setting it up

  1. In a new Zap, choose your trigger: a form, a CRM, a spreadsheet or a webhook.
  2. Add a Webhooks by Zapier POST step to the verify endpoint, with your API key in the X-API-Key header.
  3. Map the trigger's email field into the request body.
  4. Add a Filter step that continues only when the result is valid, or Paths that split valid, catch_all and the rest.
  5. Write the result and the check date back to your CRM or sheet so nothing gets checked twice.
  6. For list work, build a second Zap that polls the job until it completes.

Zapier: common questions

Can I connect an email verifier to Zapier to check new leads automatically?

Yes. Add a webhook step calling ZapBounce's verify endpoint after your trigger, map the email field, and filter on the result. Each check costs one credit, 1,000 checks cost $5, and unknown results cost nothing.

Does a verification cost a Zapier task?

Yes, one task per check, like any action step. For a whole list, submit a job from one task and poll for completion in a second Zap.

Can I use Make instead of Zapier?

Yes. Make's HTTP module calls ZapBounce's verify endpoint with your key in a header, and a scheduled scenario polls a job until it completes.

Should the filter continue on catch-all?

It depends on the next step. Stop catch_all before a sending step, and let it through to a CRM update that records the result.

Reference

Check a Zapier export today

100 free checks a month, no card. Unknown results are refunded.

Get an API keySee pricing