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 (Import cURL — fastest)

The quickest way to configure the node is to import a cURL command — n8n fills in the method, URL, headers, and body for you.

1. Add an HTTP Request node to your workflow and open it.
2. On the node’s Parameters tab, click the Import cURL button (top-right, just above the Method field).
3. In the Import cURL command dialog, paste the cURL below and replace YOUR_API_KEY with your key (from the API Access page).
4. Click Import. n8n auto-fills Method (POST), URL, the Authorization and Content-Type headers, and the JSON body.
5. Click Execute step (top-right) to test — the verification (status, is_valid, credits_used) appears in the OUTPUT panel.

curl -X POST https://app.validemailchecker.com/api/verify-single \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "user@example.com"}'

Step 2b — Manual setup (reusable credential)

Prefer to configure the node by hand and reuse the key across workflows? Set it up manually:

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

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.

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.