Add real-time email verification to any n8n workflow with our official MailTester Ninja node, or with a single HTTP Request node. MailTester Ninja checks each address against the recipient's mail server and returns a clear verdict, so your workflow can keep valid contacts and drop the ones that would bounce.
What you need
- n8n Cloud or self-hosted. Our official node is verified by n8n and available on n8n Cloud. The HTTP Request method works everywhere, even where community nodes are turned off.
- A key: a free API token to try it (50 checks a day, one request every 30 seconds) or a paid key for full speed. On n8n cloud, use a token rather than
key=free: the keyless tier is counted per IP, and n8n cloud shares its IP addresses between users.
Use the official node
- In the nodes panel, search for MailTester Ninja: it appears under More from the community. Select it, then click Install. An owner or admin of your n8n does this once for everyone.
- Add the MailTester Ninja node and create a MailTester Ninja API credential with your token or key.
- Choose Verify to check one address (it returns
codeandmessage) or Find to look up a work email from a first name, a last name and a company domain (paid key).
Node not listed? On n8n Cloud, turn on Verified community nodes in the instance settings of your n8n Cloud admin panel, then restart your instance. On a self-hosted n8n, open Settings, then Community nodes, then Install, and enter n8n-nodes-mailtester-ninja.
The node also works as a tool for the AI Agent. Two example workflows are on GitHub, and our Brevo page has a workflow that verifies every new Brevo contact.
Or use an HTTP Request node
- Add an HTTP Request node after the step that provides the email address.
- Set Method to
GETand URL tohttps://happy.mailtester.ninja/ninja. - Turn on Send Query Parameters and add two parameters:
email={{ $json.email }}(map it to your field) andkey= your token or key. - Run the node. It returns the JSON verdict: read
{{ $json.code }}and{{ $json.message }}in the next nodes.
Or import the ready-made workflow
Our workflow.json contains a manual trigger, the HTTP Request node already filled in, and an IF node that splits valid from invalid addresses. Download it, then in n8n choose Workflows, Import from File and set your key.
Branch on the verdict
Add an IF node after the HTTP Request, with the condition {{ $json.code }} equals ok. The true branch continues (add to your list, sync to your CRM), the false branch skips, tags or sends the contact to review.
| code | Meaning | What to do in the workflow |
|---|---|---|
| ok | Valid and deliverable | Continue. |
| ko | Invalid, will bounce | Drop or tag the contact. |
| mb | Uncertain (catch-all domain, server could not be probed) | Send to review, or decide by risk. |
-- | No verdict (key problem, or free limit reached with HTTP 429) | Retry later. Never drop the contact on this answer. |
Verify a whole list
Use Loop Over Items with a batch size of 1 and a Wait node between calls: about 1 second on Pro (11 requests per 10 seconds), 0.45 seconds on Ultimate (23 per 10 seconds), and 30 seconds with a free token.
Keep your key secret
Store the key in an n8n credential or variable instead of typing it into the node, so an exported or shared workflow never contains it.
Questions
Is there an official MailTester Ninja node for n8n?
Yes: n8n-nodes-mailtester-ninja, verified by n8n and available on n8n Cloud. It is published from GitHub Actions with npm provenance. The HTTP Request node remains a good option when you cannot install community nodes.
Is anything stored?
No. Each address is checked in real time and we keep no copy of the addresses you verify.
Try it now
Get a free API token, or see the plans for up to 200,000 checks a day. Full reference: API documentation and OpenAPI specification. Back to all integrations.
