Currents email verification with BillionVerify
Currents is an analytics platform that helps teams track and understand user behavior and engagement data. By integrating BillionVerify, you can ensure that user email addresses flowing into your analytics pipelines are valid — keeping your user records clean and your event data tied to real, reachable people.
Why verify before the send
Analytics platforms are only as reliable as the data they ingest. If invalid or fake email addresses enter your Currents workspace, they skew cohort analysis, inflate user counts, and create noise in engagement metrics. Verifying emails upstream means your behavioral data reflects genuine users — making every insight more trustworthy.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Currents sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Currents + 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 Currents contacts",
"message": "Replace this Gmail send with your Currents 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 Currents
Ready-to-use workflows that verify emails before Currents sends.
How it works
- 1
Integrate BillionVerify with your data pipeline feeding Currents using the REST API or the n8n community node.
- 2
When a user registers or an email field is captured, trigger a BillionVerify API call to validate the address.
- 3
BillionVerify returns a result indicating whether the address is valid, disposable, a role account, or a catch-all.
- 4
Pass the verification status as a user property or trait into Currents, enriching your analytics context.
- 5
Use the verification flag in Currents to filter segments, build cleaner cohorts, and produce more accurate reports.
When to use this
Validate Emails at User Registration
Before a new user record is written to Currents, BillionVerify confirms the email is real and deliverable. This prevents disposable addresses and bots from entering your analytics dataset and distorting retention or activation metrics.
Enrich User Profiles with Verification Status
Append a verification status field to user profiles in Currents. Segment your analytics by verified vs. unverified users to compare engagement patterns and identify how email quality correlates with long-term product adoption.
FAQ
Why does email verification matter for an analytics platform like Currents?
Fake or invalid emails generate phantom users that corrupt cohort and funnel analyses. Clean email data ensures your metrics reflect actual human behavior, making product decisions based on that data far more reliable.
Can BillionVerify be called in real time before data is written to Currents?
Yes. The REST API responds in milliseconds, making it suitable for inline validation before user records or events are committed to your analytics pipeline.
Does BillionVerify store the emails I verify?
BillionVerify processes emails for verification purposes and handles data in accordance with its privacy policy. You retain full control over your user data within Currents.
Verify emails in Currents
Create a free account, grab your API key, and stop bounces before they happen.
Get started free