How to verify emails and phone numbers in Zapier, Make and n8n

Updated 2026-10-19 · 6 min read

You don't need to write code to verify the emails and phone numbers flowing into your CRM, spreadsheet or newsletter tool. Zapier, Make and n8n can all call the Verified.net API with their built-in HTTP steps. This guide shows the setup for each, plus the filter that keeps bad contacts out.

You'll need an API key: sign up, then create one under API keys. Treat it like a password.

The request, for every tool

The answer's recommendation.action field is accept, review or reject. That's the one field your filter needs. 1 credit per email, 1 per phone number.

Zapier

1. Trigger: wherever new contacts appear (new form entry, new row in Google Sheets, new HubSpot contact...).
2. Add an action: Webhooks by Zapier → Custom Request (Webhooks is included in Zapier's paid plans).
3. Method POST, URL https://api.verified.net/v1/email.
4. Data: {"address": " then insert the email field from your trigger, then "}.
5. Headers: Authorization = Bearer YOUR_API_KEY and Content-Type = application/json.
6. Test the step. You'll see fields such as Recommendation Action, Did You Mean and Checks Disposable.
7. Add Filter by Zapier: continue only if Recommendation Action (Text) Does not exactly match reject.
8. Then your real action (add to the mailing list, create the CRM contact).

Prefer to tag rather than drop? Use Paths by Zapier: one path for reject (tag as "bad email"), one for everything else.

Make

1. Add the HTTP → Make a request module after your trigger.
2. URL https://api.verified.net/v1/email, Method POST.
3. Headers: Authorization = Bearer YOUR_API_KEY.
4. Body type Raw, Content type JSON (application/json), Request content: {"address": "{{1.email}}"} (map your trigger's email field).
5. Tick Parse response so later modules can use the fields.
6. On the link to the next module, add a filter: Data: recommendation: action Not equal to reject.

n8n

1. Add an HTTP Request node. Method POST, URL https://api.verified.net/v1/email.
2. Authentication: Generic Credential Type → Header Auth. Create a credential with Name Authorization and Value Bearer YOUR_API_KEY. Stored as a credential, the key stays out of your workflow JSON.
3. Send Body: on, Body Content Type JSON, Specify Body Using Fields Below, name address, value {{ $json.email }}.
4. Add an If node: {{ $json.recommendation.action }} is not equal to reject.

For large batches in n8n, set the HTTP Request node's Batching option (for example 50 items per batch) to stay well under the rate limit of 200 requests per 10 seconds.

Cleaning a whole list instead

For a one-off clean of an existing list (thousands of rows), automation steps are slow and use a task per row. Upload the CSV to Bulk in the dashboard instead: up to 100,000 rows, duplicates charged once, and you download the same file back with result columns added. The bulk API can also notify a Zapier, Make or n8n webhook when a job finishes (bulk webhooks).

Tips

• Don't stop the whole workflow on errors. In Zapier and Make, set the HTTP step to continue on error, so a timeout doesn't drop a real lead.
• Use the typo fix. If did_you_mean is set (for example gmail.com for gmial.com), store it in a note or use it instead.
• Same contact twice is free within 7 days, so re-running a workflow doesn't double-charge.