Verifyre

Zapier integration

Verify every lead before the next Zap step.

Zapier moves leads between 6,000 apps; Verifyre makes sure the email on each one actually works. A Webhooks by Zapier step and a Filter are all it takes.

Zapier logo
Get an API key Setup guide

What it does

Verifyre and Zapier, together.

One GET request

Webhooks by Zapier calls the Verifyre API with the email from your trigger and gets back status, reason, score, provider and a typo suggestion as mapped fields.

Filter or branch

Continue only for deliverable addresses, or route risky ones to a review sheet with Paths. Every field in the response is available to later steps.

Works with any trigger

Typeform, Facebook Lead Ads, Gravity Forms, Shopify, Calendly, Stripe: wherever the email comes from, it is verified before it is written anywhere.

Setup guide

Set up Zapier in 3 steps.

You will need a Verifyre account (free, 100 credits) and an API key from Settings, then API keys.

  1. Add a Webhooks by Zapier step

    After your trigger, add the action Webhooks by Zapier with the event GET. Fill it in as below, mapping the email field from the trigger into the query string and putting your Verifyre key in the Authorization header.

    text
    App:       Webhooks by Zapier
    Event:     GET
    URL:       https://verifyre.co/api/v1/verify
    Query:     email  ->  {{Email}}            (map the field from your trigger)
    Headers:   Authorization  ->  Bearer vfy_live_YOUR_API_KEY
    Unflatten: yes
  2. Test and map the response

    Click Test step. Zapier shows the JSON response unflattened: status, reason, reason_text, score, did_you_mean, provider and the checks object are now available to every later step.

  3. Filter on the verdict

    Add Filter by Zapier so the Zap only continues for deliverable addresses (or for scores above 59 if you want catch-all domains too). Undeliverable leads can go down a separate Path to a Google Sheet for review.

    text
    Filter by Zapier
      Only continue if...
      (Text) Status   exactly matches   deliverable
    
    Alternative, keep risky too:
      (Number) Score  greater than      59

Write-back

What gets written back to your stack.

Verification only reads. Writing results back is a separate step you trigger after reviewing the counts, and nothing is ever deleted without your say-so.

  • Nothing is written to Verifyre; the verdict flows into your Zap as fields you map wherever you like: a custom field in HubSpot, a tag in Mailchimp, a column in Sheets.
  • did_you_mean lets you fix typos in the same Zap: a Formatter step can replace the domain before the lead is created.

Zapier FAQ

Zapier questions

Visit the help centre
Is there a native Verifyre app on Zapier?
The webhook step is the fastest and most flexible route and needs no approval from anyone. A native app is on the roadmap; the webhook will keep working regardless.
How many tasks does this use?
One task for the webhook step and one for the filter, per lead, on Zapier's side. On Verifyre's side it is one credit per unique address; repeat checks inside 24 hours are free.
Can I verify in bulk from Zapier?
For lists use POST /api/v1/bulk with up to 50,000 addresses, then let the callback_url trigger a Catch Hook in Zapier when the job finishes.

Connect Zapier in two minutes.

100 free verifications on signup, no card. Keep them for your first sync.

Get an API key See pricing