Validate emails in your n8n workflows
Add the Mail7 node to any n8n workflow and check an address in flight. It returns Valid, Not Valid or Unknown, so you route confirmed-invalid contacts out and keep the genuine ones.
Community node, publication pending - install it into your n8n instance directly today.
The Mail7 node for n8n
The node takes an email from any previous step and returns a structured validation result. It works the same on n8n Cloud and self-hosted instances, and needs only an optional API key for higher volume.
Three-way output for clean branching logic
Rather than a single true or false that hides uncertainty, the node outputs three states you can wire straight into an IF or Switch node:
Mailbox confirmed. Continue.
Confirmed invalid. Route out.
Unconfirmed. Keep, do not reject.
Route Not Valid out, keep Unknown in
A good default is to send only Not Valid results down a cleanup branch and let Valid and Unknown proceed. Unknown covers catch-all domains, greylisting and servers that block SMTP probing, none of which mean the address is fake.
Typical self-hosted use cases
Clean incoming leads before they reach a database, validate addresses pulled from a webhook, or run a scheduled workflow that re-checks a list and quarantines the confirmed-invalid ones. The node fits wherever your workflow already handles email.
Install the node in your n8n instance
-
1
Add the community node
Publication is pending, so install the node package into your n8n instance directly.
-
2
Add it to a workflow
Drop the Mail7 node after the step that produces the email.
-
3
Branch on the output
Use IF or Switch on the Valid / Not Valid / Unknown result.
Free single checks, paid plans for volume
Single checks are free and need no account. Paid plans raise your API volume for busy automations, and you are only charged for definite Valid and Not Valid results. Unknown checks are always free.
Related integrations
Frequently asked questions
Is it a community node?
Yes. Publication to the community catalog is pending, so for now you install it into your n8n instance directly.
What does the node output?
Valid, Not Valid or Unknown for each email, ready to branch on.
Does Unknown mean the email is bad?
No. It means unconfirmed (catch-all, greylisting, blocked SMTP) and should not be treated as invalid.
Are Unknown results billed?
No, they are free and never counted.
What if the API call fails?
The node is fail-open so your workflow continues.