Verify emails in n8n
Use the HTTP Request node with a saved Bearer credential to check each item, then branch on status with an If or Switch node.
Setup
- Create an API key at simpleverifier.com/api-keys. It starts with sv_live_. API access comes with selected paid plans; a key on a plan without it gets a 402 that says so.
- In n8n, create a Header Auth credential named SimpleVerifier with Name Authorization and Value Bearer followed by your key.
- Add an HTTP Request node. Method GET, URL https://simpleverifier.com/api/v1/verify, enable Send Query Parameters and add email set to your email field expression.
- Set Authentication to Generic Credential Type, Header Auth, and pick the credential. Set the timeout to 40 seconds.
- Execute the node. Each item gets status, reason, send_advice and reason_detail.
- Add an If node on status equal to valid. Send true to your next step and false to a tag or log step.
Using the result
Route on the status field: valid means the mail server confirmed the mailbox, risky means delivery could not be confirmed (catch-all domain, role address, provider that hides mailbox status), invalid means it will bounce or is a throwaway address. Keep risky out of cold sequences unless you accept the bounce risk.
Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.
Common questions
- Which plans include API access for n8n?
- API access comes with selected paid plans, listed on the pricing page. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.
- Is there a SimpleVerifier node for n8n?
- Not yet in the n8n node list. The HTTP Request node covers it today. See also the guide at /blog/verify-emails-n8n.
- Can an n8n AI agent use it?
- Yes, through our MCP server at /docs/mcp, or by exposing the HTTP Request node as a tool.