Agent email verification with BillionVerify
Agent is an AI automation platform for building intelligent, multi-step workflows. Integrating BillionVerify into your Agent pipelines ensures that any email address collected, enriched, or passed between workflow steps is deliverable before it reaches an outreach or storage action.
Why verify before the send
AI agents often gather email addresses from diverse sources — web scraping, form submissions, data enrichment APIs — where quality is unpredictable. Sending to unverified addresses risks bounces, spam complaints, and domain blacklisting. Adding BillionVerify as a verification step inside your agent workflow eliminates these risks before they compound across automated runs.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Agent sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Agent + 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 Agent contacts",
"message": "Replace this Gmail send with your Agent 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 Agent
Ready-to-use workflows that verify emails before Agent sends.
How it works
- 1
Add BillionVerify to your Agent workflow via the n8n community node, Integrately, or the REST API.
- 2
Identify the workflow step where email addresses first appear — collection, enrichment, or pre-send.
- 3
Call BillionVerify with the email and receive a status and detailed sub-status in return.
- 4
Branch your workflow based on the result: proceed for valid, hold for catch-all, discard for invalid.
- 5
Log verification outcomes alongside contact records for auditing and list hygiene reporting.
When to use this
Verify emails mid-workflow before sending
Insert a BillionVerify check between your data-collection step and your email-sending step inside Agent. Only addresses that pass verification move forward, keeping bounce rates low regardless of where the data originated.
Enrich and clean contact data in real time
When an Agent workflow builds a contact record from multiple sources, verify the assembled email address with BillionVerify before writing it to a CRM or database. Catch invalids before they pollute downstream systems.
Gate lead scoring on email deliverability
Use BillionVerify's sub-status fields within an Agent scoring workflow to downgrade leads with role-based or catch-all addresses, ensuring your sales team focuses on the most reachable prospects.
FAQ
Can I use BillionVerify inside an automated AI agent loop?
Yes. BillionVerify's REST API is stateless and fast, making it well-suited for repeated calls inside agent loops that process contacts one at a time or in batches.
What sub-statuses does BillionVerify return?
BillionVerify returns sub-statuses such as mailbox-not-found, disposable, role-based, catch-all, and syntax-error, giving your workflow enough detail to apply different actions per risk type.
How do I handle catch-all addresses in my agent workflow?
Catch-all addresses cannot be confirmed as deliverable, so a common approach is to route them to a separate lower-priority list or exclude them from cold outreach while still using them for warm sequences.
Is there rate limiting on the BillionVerify API?
Limits depend on your plan. For high-throughput agent workflows, the bulk endpoint is more efficient than individual calls and avoids hitting per-second rate limits.
Verify emails in Agent
Create a free account, grab your API key, and stop bounces before they happen.
Get started free