Peliqan email verification with BillionVerify
Peliqan is a data integration and analytics platform that connects cloud data sources and automates data pipelines. Adding BillionVerify to Peliqan workflows ensures that email address fields flowing through your pipelines are validated and cleaned before reaching downstream dashboards, CRMs, or marketing tools.
Why verify before the send
Data pipelines amplify whatever quality goes into them. An unverified email in an upstream source propagates as a bad row across every connected system — inflating contact counts, skewing engagement analytics, and causing bounces when downstream tools attempt outreach. BillionVerify removes these errors at the pipeline level.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Peliqan sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Peliqan + 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 Peliqan contacts",
"message": "Replace this Gmail send with your Peliqan 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 Peliqan
Ready-to-use workflows that verify emails before Peliqan sends.
How it works
- 1
Integrate BillionVerify into Peliqan pipelines via the REST API, n8n, or Integrately.
- 2
Identify pipeline steps where email fields are present — such as CRM syncs, form data ingestion, or data warehouse loads.
- 3
At each step, send email values to BillionVerify for real-time or batch verification.
- 4
BillionVerify returns status codes indicating validity, disposability, catch-all, and role-based classification.
- 5
Use these results to filter, enrich, or route records before they reach destination systems.
When to use this
Cleanse Email Fields During ETL Pipelines
As Peliqan moves data between sources, add a BillionVerify step to validate email columns mid-pipeline. Invalid, disposable, or catch-all addresses are flagged or removed before the data lands in your warehouse or CRM.
Enrich Analytics Datasets with Verification Scores
Append BillionVerify's verification results — deliverability status, disposable flag, catch-all indicator — as additional columns in Peliqan's output tables. Analysts can then filter or segment contacts based on email quality in their BI tools.
FAQ
Can BillionVerify handle the high volume of records typical in data pipelines?
Yes. BillionVerify's REST API supports bulk verification, making it practical for pipeline workloads that process thousands or millions of email addresses at a time.
How do verification results integrate with Peliqan's data model?
BillionVerify returns structured JSON responses that Peliqan can map to new columns or use as filter conditions — fitting naturally into your existing transformation logic.
What is a catch-all email and why should pipelines care?
A catch-all domain accepts mail sent to any address under it, making it impossible to confirm a specific mailbox exists. Including catch-all addresses in outreach campaigns leads to high bounce rates, which BillionVerify helps you identify and manage.
Does verifying emails in Peliqan pipelines affect pipeline latency?
For real-time pipelines, BillionVerify's fast API keeps added latency minimal. For batch workloads, bulk verification runs asynchronously and results are returned together, keeping pipeline throughput high.
Verify emails in Peliqan
Create a free account, grab your API key, and stop bounces before they happen.
Get started free