Valid Email Checker

How do I verify emails in n8n?

n8n has no dedicated Valid Email Checker node, and you do not need a community node either. The built-in HTTP Request node calls any REST API, and our verification endpoint is a standard REST call. Drop it into a workflow to verify addresses as they move through your automation — vet sign-ups, scrub leads before they reach a CRM, or drop disposable addresses on the spot.

Step 1 — Get an API key

In the dashboard, open the Developer page to generate an API key. You will store it as an n8n credential rather than hard-coding it into the node. API access unlocks after your first credit purchase.

Step 2 — Add the HTTP Request node

  1. Add an HTTP Request node to your workflow.
  2. Set Method to POST and URL to https://app.validemailchecker.com/api/verify-single.
  3. Set Authentication to Generic Credential → Header Auth, then create a credential with Name Authorization and Value Bearer <API_KEY>. (n8n also offers a Bearer Auth credential type — either works; keeping the key in a credential keeps it out of the workflow JSON.)
  4. Turn on Send Body, set the body type to JSON, and provide {"email":"{{ $json.email }}"}, mapping the address from the previous node.
  5. Execute the node. n8n parses the JSON response so later nodes can read fields such as status and is_valid.
http
POST https://app.validemailchecker.com/api/verify-single
Authorization: Bearer <API_KEY>
Content-Type: application/json

{"email":"user@example.com"}

The response includes status (a deliverable address returns "safe"), is_valid (boolean), is_disposable, risk_score, and credits_used. Add an IF node after the HTTP Request node and test {{ $json.status }} equals safe to route deliverable addresses down one branch and everything else down another.

Triggering on inbound events
To start a workflow from an external event, front it with a Webhook trigger node and chain the HTTP Request node after it. Because n8n workflows export as JSON, you can save a verification workflow as a reusable, importable template and share it across instances.

Single vs. bulk

The configuration above uses the single endpoint /api/verify-single — real-time, one address per call, which is the right default for verifying records as they flow through a workflow. See Make your first API call for the complete single-verify reference.

To clean an entire list in one pass, use the bulk flow: POST an array to /api/verify-bulk ({"emails":[...],"name":"..."}) to get a task_id, then poll GET /api/get-results/{task_id} until the job completes. In n8n that is a second HTTP Request node, optionally wrapped in a Wait/loop while the task runs. See the Bulk endpoint reference for details.

Cost

One credit per email verified, identical to bulk uploads or direct API calls. Running it through n8n costs nothing extra. Unknown results — where we could not reach a definitive answer — are automatically refunded, so you only pay for conclusive verifications.

For a step-by-step walkthrough with screenshots, see the full n8n guide at validemailchecker.com/integrations/n8n.