Verify emails in Zapier
Use Webhooks by Zapier to check an address between any trigger and action, for example a new row, form entry or CRM contact, and branch on the result.
Setup
- Create an API key at simpleverifier.com/api-keys. It starts with sv_live_. API access comes with selected paid plans; a key on a plan without it gets a 402 that says so.
- In your Zap, add an action step: Webhooks by Zapier, then Custom Request.
- Set the method to POST, the URL to https://simpleverifier.com/api/v1/verify and Data to {"email": "<your email field>"}.
- Under Headers add Authorization with the value Bearer followed by your key, and Content-Type with application/json.
- Test the step. The response contains status, reason, send_advice and reason_detail.
- Add a Filter or Paths step on status. Send valid addresses on; stop or tag the rest.
Using the result
Route on the status field: valid means the mail server confirmed the mailbox, risky means delivery could not be confirmed (catch-all domain, role address, provider that hides mailbox status), invalid means it will bounce or is a throwaway address. Keep risky out of cold sequences unless you accept the bounce risk.
Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.
Common questions
- Which plans include API access for Zapier?
- API access comes with selected paid plans, listed on the pricing page. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.
- Is there a SimpleVerifier app in the Zapier directory?
- Not yet. This guide uses Webhooks by Zapier, which needs a Zapier plan that includes it.
- Can I validate phone numbers too?
- Yes. POST to https://simpleverifier.com/api/v1/phone with {"phone": "...", "country": "US"}. It checks format and numbering-plan line type; it never says a number is in service.