Affinity Trigger email verification with BillionVerify
Affinity Trigger fires automations when relationship data changes in your Affinity CRM. Pairing it with BillionVerify ensures every email address that enters your pipeline is valid before your team acts on it, protecting deliverability and keeping contact records clean.
Why verify before the send
CRM contact lists grow quickly through imports, web forms, and enrichment tools, and bad addresses accumulate just as fast. Verifying emails at the point of entry stops bounces from damaging your sender reputation, removes disposable or role-based addresses that will never convert, and keeps your Affinity data trustworthy for the whole team.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Affinity Trigger sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Affinity Trigger + 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 Affinity Trigger contacts",
"message": "Replace this Gmail send with your Affinity Trigger 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 Affinity Trigger
Ready-to-use workflows that verify emails before Affinity Trigger sends.
How it works
- 1
Connect Affinity Trigger and BillionVerify inside your n8n workflow or via Integrately.
- 2
Choose the trigger event — such as contact created or list updated — in Affinity Trigger.
- 3
Map the email field from the Affinity payload to the BillionVerify verification step.
- 4
BillionVerify returns a result with status, sub-status, and risk flags for each address.
- 5
Use conditional logic to tag, skip, or alert on addresses that fail verification before they reach your team.
When to use this
Validate new contacts on creation
When Affinity Trigger detects a new person or organization added to your CRM, BillionVerify checks the email immediately. Invalid or risky addresses are flagged so your team follows up only on deliverable contacts.
Clean imported deal contact lists
Bulk imports from data providers often contain stale or fake emails. Route each imported address through BillionVerify before syncing to Affinity, so your pipeline reflects only reachable prospects from day one.
FAQ
Does this work with n8n's Affinity Trigger node?
Yes. Install the BillionVerify community node in n8n and add it after any Affinity Trigger node to verify emails in the same workflow without leaving the platform.
What types of addresses does BillionVerify catch?
BillionVerify detects invalid, disposable, role-based, and catch-all addresses, giving you granular sub-statuses to apply different rules for each risk category.
Can I verify emails in bulk from an Affinity list export?
Absolutely. Upload a CSV through the BillionVerify REST API or dashboard and import the cleaned results back into Affinity to refresh your existing contact records.
Verify emails in Affinity Trigger
Create a free account, grab your API key, and stop bounces before they happen.
Get started free