Autopilot email verification with BillionVerify
Autopilot is a visual marketing automation platform for building multi-channel customer journeys across email, SMS, and in-app messaging. The quality of contact data feeding into those journeys directly shapes their effectiveness. BillionVerify ensures every email address entering your Autopilot journeys is valid and deliverable before it can cause a bounce.
Why verify before the send
Invalid addresses flowing into Autopilot journeys generate hard bounces that damage your sending domain and distort journey analytics. BillionVerify filters out dead mailboxes, disposable addresses, and suspicious role accounts at the entry point — so your Autopilot automations run on clean contact data from the start.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Autopilot sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Autopilot + 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 Autopilot contacts",
"message": "Replace this Gmail send with your Autopilot 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 Autopilot
Ready-to-use workflows that verify emails before Autopilot sends.
How it works
- 1
Set up BillionVerify via the n8n community node, Integrately's 1-click connection, or the REST API.
- 2
Trigger a verification step whenever a new contact is added to Autopilot — via webhook, API event, or CRM sync.
- 3
BillionVerify evaluates the address for deliverability, disposable-domain flags, role-address patterns, and catch-all server behavior.
- 4
Use the verification result to decide whether the contact proceeds into the Autopilot journey or is held for review.
- 5
Log risk flags back to the Autopilot contact record as a custom field for future segmentation.
When to use this
Validate contacts at journey entry
Before a new lead enters an Autopilot journey, verify their email with BillionVerify via n8n. Contacts with invalid or risky addresses can be routed to a separate clean-up journey or simply excluded, protecting the main sequence from bounce-generating entries.
Protect SMS and email cross-channel campaigns
Autopilot's multi-channel journeys depend on accurate contact records. Running email verification through BillionVerify ensures the email leg of every cross-channel campaign reaches a real inbox, keeping overall campaign metrics meaningful.
FAQ
Can I verify emails without disrupting live Autopilot journeys?
Yes. Verification integrates at the contact creation or import stage, before journey entry. Existing in-progress journeys are not affected, and future entrants are verified before they can generate bounces.
What address types does BillionVerify flag?
BillionVerify identifies invalid syntax, non-existent mailboxes, disposable email domains, role addresses such as noreply@ or admin@, and catch-all mail servers — giving you a layered risk picture for each contact.
Do I need a developer to set this up?
Not necessarily. Integrately offers a 1-click integration between BillionVerify and common automation platforms. For Autopilot-specific flows, the n8n community node requires minimal configuration and no custom code.
Verify emails in Autopilot
Create a free account, grab your API key, and stop bounces before they happen.
Get started free