This is an n8n community node. It lets you use BillionVerify email verification in your n8n workflows.
BillionVerify validates email addresses in real time — checking syntax, MX records, and live SMTP mailboxes — and flags disposable, catch-all, and role-based addresses so you can clean lists and stop bounces before they hurt your sender reputation.
n8n is a fair-code licensed workflow automation platform.
Installation Operations Credentials Usage Resources
Follow the installation guide in the n8n community nodes documentation.
In short, from the n8n UI: Settings → Community Nodes → Install and enter:
n8n-nodes-billionverify
| Operation | Description | Credits |
|---|---|---|
| Verify Email | Validate a single email address in real time. Returns status (valid, invalid, risky, catchall, role, disposable, unknown), deliverability, score, MX data, and the reason. |
1 credit (0 for unknown) |
| Verify Emails (Bulk) | Validate up to 50 email addresses in one synchronous call. Each email is emitted as a separate output item. | 1 credit per email |
| Check Disposable | Detect whether an email uses a disposable/temporary domain. In-memory lookup only. | Free |
For lists larger than 50 emails, use the asynchronous file verification API (CSV/XLSX upload + webhook callback). It is on the roadmap for this node; in the meantime call it directly via the HTTP Request node — see the API docs.
This node is exposed as an AI tool (usableAsTool). Attach it to an n8n AI Agent and the agent can verify email addresses on demand — e.g. "clean this list of leads before adding them to the CRM."
You need a BillionVerify API key.
- Sign up at billionverify.com.
- Go to Dashboard → API Keys and create a key (it starts with
sk_). - In n8n, create new BillionVerify API credentials and paste the key.
The credential test calls the free disposable-check endpoint, so validating your key costs no credits.
A common pattern: Webhook (form submission) → BillionVerify (Verify Email) → IF is_deliverable is true → add to CRM, otherwise route to a review branch.
The single-verify response looks like:
{
"email": "user@example.com",
"status": "valid",
"score": 0.95,
"is_deliverable": true,
"is_disposable": false,
"is_catchall": false,
"is_role": false,
"domain": "example.com",
"reason": "smtp_deliverable",
"credits_used": 1
}