Integrations
n8n integration
Check an email address in any n8n workflow with the built-in HTTP Request node, then branch on the result with an If or Switch node. Your key is stored as an n8n credential, so it stays out of the workflow itself.
- Status: Setup guide
- The HTTP Request node, nothing to install
Method POST
URL https://api.email-validation.org/v1/validate
Authentication Generic Credential Type: Header Auth
Name Authorization
Value Bearer ev_live_…
Send Body JSON
email {{ $json.email }}At a glance.
- Status
- Setup guide. Not listed on a marketplace yet: you set it up yourself in a few steps, below and in the full guide.
- For
- Developers and operations teams who run n8n, in the cloud or on their own server, and want addresses checked inside their workflows.
- You need
- An n8n workflow with an item that holds an email address, and an API key made for it, with a daily credit cap.
- Costs
- 1 credit = 1 validated address, as with any API request. Free: unknown results, API errors, malformed addresses and test addresses on sandbox.email-validation.org.
- Full guide
- Read the full setup guide
Typical uses.
Check form sign-ups
Validate each address a webhook or form trigger brings in, before it reaches your database or your CRM.
Branch on the result
Follow with an If or Switch node on status or action: continue for valid, review catch_all and unknown, drop invalid and disposable.
Clean an export
Run a list of addresses through the node item by item, or send the whole list as one bulk list.
Set it up. 4 steps.
The short version of the full setup guide, which stays the reference when a step does not match what you see.
Add an HTTP Request node
Method POST, URL
https://api.email-validation.org/v1/validate.Store your key
Authentication: Generic Credential Type, Header Auth, with the name
Authorizationand the valueBearerand your key.Send the address
Send Body: JSON, with a field
emailset to an expression such as{{ $json.email }}.Branch
Follow with an If or Switch node on status or action.
Good to know.
- Map
status,reason,actionanddid_you_meaninto later steps; statuses and reasons explains each value. - Use a key made for n8n, with a daily credit cap, so a looping workflow cannot spend more than you expect.
- For EU data residency, send the request to
https://api-eu.email-validation.orginstead: the same key works on both. - For a whole list at once, send it as one bulk list and get a webhook when it is done.
- Try it first with
accepted@sandbox.email-validation.organd the other test addresses: each returns the result its name says and costs nothing.
Updated · Maintained by the email-validation.org team