Company Enrich email verification with BillionVerify
Company Enrich enriches contact and company records with firmographic data, making it a staple in sales and marketing automation workflows. BillionVerify adds a critical layer of email validation, ensuring the email addresses attached to enriched records are real and reachable before outreach begins.
Why verify before the send
Data enrichment adds value to contact records, but it cannot guarantee that the email fields are deliverable. Enriched lists frequently contain role addresses, catch-all domains, or outdated mailboxes. Running BillionVerify after enrichment and before any outreach means your sales sequences target only contacts you can actually reach.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Company Enrich sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Company Enrich + BillionVerify",
"nodes": [
{
"parameters": {},
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
240,
300
],
"name": "When clicking ‘Test workflow’"
},
{
"parameters": {
"assignments": {
"assignments": [
{
"id": "email-field",
"name": "email",
"value": "jane@example.com",
"type": "string"
}
]
},
"options": {}
},
"type": "n8n-nodes-base.set",
"typeVersion": 3.4,
"position": [
460,
300
],
"name": "Get contacts"
},
{
"parameters": {
"sendTo": "={{ $json.email }}",
"subject": "Message for Company Enrich contacts",
"message": "Replace this Gmail send with your Company Enrich node — only deliverable, verified contacts reach it.",
"options": {}
},
"type": "n8n-nodes-base.gmail",
"typeVersion": 2.1,
"position": [
900,
300
],
"name": "Send email",
"webhookId": "",
"credentials": {
"gmailOAuth2": {
"id": "",
"name": "Gmail account"
}
}
},
{
"parameters": {
"operation": "verify",
"email": "={{ $json.email }}",
"additionalOptions": {}
},
"type": "n8n-nodes-billionverify.billionVerify",
"typeVersion": 1,
"position": [
540,
300
],
"name": "Verify Email (BillionVerify)",
"credentials": {
"billionVerifyApi": {
"id": "",
"name": "BillionVerify account"
}
}
},
{
"parameters": {
"conditions": {
"options": {
"caseSensitive": true,
"leftValue": "",
"typeValidation": "loose"
},
"combinator": "and",
"conditions": [
{
"id": "is-deliverable",
"leftValue": "={{ $json.is_deliverable }}",
"rightValue": "",
"operator": {
"type": "boolean",
"operation": "true",
"singleValue": true
}
}
]
}
},
"type": "n8n-nodes-base.if",
"typeVersion": 2,
"position": [
720,
300
],
"name": "IF deliverable"
}
],
"connections": {
"When clicking ‘Test workflow’": {
"main": [
[
{
"node": "Get contacts",
"type": "main",
"index": 0
}
]
]
},
"Get contacts": {
"main": [
[
{
"node": "Verify Email (BillionVerify)",
"type": "main",
"index": 0
}
]
]
},
"Verify Email (BillionVerify)": {
"main": [
[
{
"node": "IF deliverable",
"type": "main",
"index": 0
}
]
]
},
"IF deliverable": {
"main": [
[
{
"node": "Send email",
"type": "main",
"index": 0
}
],
[]
]
}
},
"settings": {
"executionOrder": "v1"
}
}Workflow templates with Company Enrich
Ready-to-use workflows that verify emails before Company Enrich sends.
How it works
- 1
Trigger your n8n workflow when a new contact record is created or updated.
- 2
Run the Company Enrich node to append firmographic and contact data to the record.
- 3
Pass the enriched email address to the BillionVerify node for real-time validation.
- 4
BillionVerify returns the address status — valid, invalid, disposable, role, or catch-all.
- 5
Write only verified contacts to your CRM or sales sequencing tool; route others to a review queue.
When to use this
Validate emails immediately after enrichment
After Company Enrich appends contact data to a record, pass the email address through BillionVerify. This two-step process ensures every enriched contact has a verified, deliverable inbox before entering a sales sequence.
Filter role accounts from enriched B2B lists
Enriched datasets often include generic role addresses like info@ or sales@. BillionVerify identifies and flags these so your CRM only stores individual contacts suited for personalised outreach.
Maintain CRM hygiene as new records flow in
Build a continuous workflow where every new enriched contact is verified by BillionVerify before being written to your CRM. This prevents bad data from accumulating and avoids costly list-cleaning campaigns later.
FAQ
Can't data enrichment tools guarantee email accuracy on their own?
Enrichment tools focus on finding contact data, not on verifying real-time deliverability. Mailboxes close, domains expire, and role addresses accumulate. BillionVerify checks the current state of each address independently.
What is a role address and why should I filter it out?
Role addresses like info@, support@, or admin@ are shared inboxes monitored by teams. They often trigger spam complaints and rarely convert. BillionVerify flags them so you can exclude them from personalised outreach.
How do I set this up in n8n?
Install the BillionVerify community node, add it after your Company Enrich step in the workflow, and map the email field. Verified addresses flow to your CRM node; invalid ones go to a separate branch for review.
Is there a way to verify in bulk rather than one at a time?
Yes. Use BillionVerify's bulk REST API endpoint to verify entire enriched lists at once, then import the results back into your workflow to split valid from invalid records.
Verify emails in Company Enrich
Create a free account, grab your API key, and stop bounces before they happen.
Get started free