Email verification in Zapier, Make and n8n

The request all three tools send

Whichever tool you use, the step makes the same GET request. Map the email field from your trigger into the email parameter, and keep the API key in the tool's credential or secret store rather than in the step itself if it offers one.

Method:   GET
URL:      https://app.veridock.io/v1/verify
Query:    email = <the address from your trigger>
Header:   Authorization = Bearer vd_live_your_key

Zapier

Use Webhooks by Zapier, which needs a paid Zapier plan.

• Add an action, choose Webhooks by Zapier, and pick the GET event.
• Set the URL to the verify endpoint, and add email under Query String Params with the value from your trigger.
• Add Authorization under Headers, with the value Bearer followed by your key.
• Test the step, then add a Filter or Paths step on the status field it returns.

Make

Use the HTTP app's Make a request module.

• Add the module, set the URL to the verify endpoint and the method to GET.
• Under Headers, add Authorization with the value Bearer followed by your key.
• Under Query String, add email and map it from the previous module.
• Turn on Parse response so later modules can read status, then add a Router with a filter for each outcome.

n8n

Use the HTTP Request node, which works the same way on n8n Cloud and self-hosted.

• Set Method to GET and URL to the verify endpoint.
• Under Authentication, choose Generic Credential Type and Header Auth, with the name Authorization and the value Bearer followed by your key.
• Under Send Query Parameters, add email with an expression such as {{ $json.email }}.
• Add a Switch node on {{ $json.status }} to route each result.

Route each result

Every response has one of four statuses. Handling all four keeps real leads out of the bin.

• deliverable: continue to your CRM or email list.
• undeliverable: do not send. Remove it, or tag it for review.
• risky: tag it and decide by reason. A role account may be fine for B2B, and a disposable address probably is not.
• unknown: the server gave no clear answer, and you are not billed. Retry later rather than deleting it.

Avoid wasting credits and tasks

Put a filter before the HTTP step so empty email fields never reach it, and run it on new records only rather than on every update. For a whole list, upload a CSV in the dashboard or use the bulk API instead of looping a list through your automation tool, which also spends a task for each row.