Acquire email verification with BillionVerify
Acquire is a customer engagement platform that unifies live chat, co-browse, and support across channels. Every visitor conversation that captures an email is an opportunity for a bounce—connecting BillionVerify ensures those addresses are real before they enter your CRM or trigger automated follow-ups.
Why verify before the send
Support and chat platforms collect email addresses in high-friction moments when visitors are typing quickly or on mobile. Typos, temporary addresses, and role accounts are common. Letting unverified emails flow into your CRM inflates your contact database with dead weight and erodes the deliverability of every campaign that touches those records.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Acquire sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Acquire + 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 Acquire contacts",
"message": "Replace this Gmail send with your Acquire 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 Acquire
Ready-to-use workflows that verify emails before Acquire sends.
How it works
- 1
Connect Acquire to BillionVerify through the n8n community node, Integrately, or the REST API.
- 2
When a visitor submits an email in an Acquire chat widget or form, the address is sent to BillionVerify.
- 3
BillionVerify validates syntax, checks domain MX records, probes SMTP reachability, and screens for disposable and catch-all domains.
- 4
The verification result is returned immediately with a status label.
- 5
Valid addresses proceed to your CRM or automation workflow; risky or invalid ones are flagged or discarded based on your rules.
When to use this
Validate chat lead captures in real time
When a visitor submits their email to start a chat or request a callback in Acquire, BillionVerify checks the address instantly. Invalid or disposable emails are flagged before the contact is created, keeping your CRM accurate from the first touchpoint.
Filter sign-up emails before onboarding sequences
Trial or demo requests captured through Acquire often trigger onboarding email sequences. Verifying each address before the sequence starts prevents bounces that could affect your sending domain's reputation.
FAQ
How does BillionVerify connect to Acquire?
You can integrate via the n8n community node for workflow automation, Integrately for a no-code 1-click setup, or call BillionVerify's REST API directly from any custom Acquire webhook or integration.
What is a catch-all email address and why does it matter?
A catch-all domain accepts every email sent to it regardless of whether the specific mailbox exists. Sending to catch-all addresses risks bounces and deliverability damage. BillionVerify flags them so you can decide how to handle them.
Does verifying emails impact the customer experience in Acquire?
Not noticeably. Verification happens in the background via API and completes in milliseconds, so visitors experience no delay when submitting their email in a chat widget.
Verify emails in Acquire
Create a free account, grab your API key, and stop bounces before they happen.
Get started free