Google Contacts email verification with BillionVerify
Google Contacts is Google's contact management service, used by individuals and teams to store and organize personal and business contacts. When email addresses in Google Contacts power outreach campaigns or automated messages, verifying them with BillionVerify first ensures every send reaches a real, active inbox.
Why verify before the send
Contact books accumulate outdated, mistyped, and defunct email addresses over time. Sending to stale Google Contacts without verification leads to bounces that damage your sender reputation and can get your domain flagged by email providers. BillionVerify identifies undeliverable addresses so you can clean your contacts before any campaign or sync.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Google Contacts sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Google Contacts + 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 Google Contacts contacts",
"message": "Replace this Gmail send with your Google Contacts 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 Google Contacts
Ready-to-use workflows that verify emails before Google Contacts sends.
How it works
- 1
Connect Google Contacts and BillionVerify via n8n, Integrately, or a custom REST API integration.
- 2
Export or stream contact email addresses from a selected Google Contacts group or label.
- 3
BillionVerify checks each address for syntax errors, domain validity, disposable-inbox patterns, and catch-all domains.
- 4
Contacts with verified addresses are passed to your email tool or retained in the book; unverified ones are flagged for review or removal.
- 5
Schedule regular re-verification runs to catch addresses that have become invalid since they were first added.
When to use this
Verify contacts before syncing to an email platform
Before pushing a Google Contacts group into Mailchimp, ActiveCampaign, or another email platform, run the list through BillionVerify. Remove invalid and disposable addresses so your import starts clean and your campaign metrics reflect genuine engagement.
Keep a shared team contact book accurate
Teams using Google Contacts as a shared CRM-lite can schedule periodic BillionVerify audits to flag or remove contacts whose email addresses are no longer valid, preventing wasted outreach and protecting the sender domain's reputation.
Validate new contacts added from form submissions
When a workflow automatically adds a new contact to Google Contacts from a web form or lead source, verify the email address with BillionVerify first. Only confirmed, deliverable addresses make it into the contact book.
FAQ
How often should I verify my Google Contacts list?
For active outreach lists, quarterly verification is a reasonable baseline. If contacts come from diverse or external sources, verify them at the point of entry and again before each major campaign send.
Can BillionVerify detect catch-all addresses in Google Contacts?
Yes. Catch-all domains accept any email regardless of whether the mailbox exists, so messages sent to them often bounce silently. BillionVerify flags catch-all addresses so you can decide how to handle them before sending.
What is the easiest way to connect Google Contacts to BillionVerify?
Integrately offers a 1-click integration that requires no code. Alternatively, the n8n community node provides a visual workflow builder, and the REST API gives full programmatic control for custom automation.
Will verification remove contacts from Google Contacts automatically?
BillionVerify returns verification results; what happens next is controlled by your workflow. You can configure it to delete, label, or export flagged contacts depending on your preferred cleanup process.
Verify emails in Google Contacts
Create a free account, grab your API key, and stop bounces before they happen.
Get started free