Convertapi email verification with BillionVerify
ConvertAPI is a developer-focused file conversion service for transforming documents, images, and data formats through a REST API. When your ConvertAPI workflows handle contact data or email lists, integrating BillionVerify through n8n or Integrately ensures email addresses are validated as part of the same automated pipeline.
Why verify before the send
Developer pipelines that process or redistribute email data need clean inputs. Forwarding unverified addresses to CRMs, marketing platforms, or storage systems silently propagates bad data. BillionVerify catches invalid, disposable, and role addresses at the pipeline level, before they reach any downstream API or database.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Convertapi sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in ConvertAPI + 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 ConvertAPI contacts",
"message": "Replace this Gmail send with your ConvertAPI 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 Convertapi
Ready-to-use workflows that verify emails before Convertapi sends.
How it works
- 1
Incorporate BillionVerify into your n8n or Integrately automation alongside ConvertAPI, or call the BillionVerify REST API directly from your backend.
- 2
After ConvertAPI processes a file and email fields are extracted, pass each address to BillionVerify for verification.
- 3
BillionVerify checks syntax, domain DNS records, disposable email detection, role-address patterns, and catch-all behavior.
- 4
Each address receives a machine-readable verdict your pipeline can act on.
- 5
Verified results are merged back into the converted output or used to filter the dataset before it moves to the next step.
When to use this
Validate emails extracted from converted documents
When ConvertAPI extracts or converts data containing email fields — from PDFs, spreadsheets, or form exports — pipe those addresses through BillionVerify before storing or acting on them. Only verified contacts reach your downstream systems.
Enrich conversion outputs with verification status
Append a BillionVerify result field to each record before ConvertAPI packages it in the target format. Consumers of the output file immediately know which addresses are safe to contact.
FAQ
Is BillionVerify available as a REST API that I can call from my own backend?
Yes. BillionVerify offers a REST API with both single-address and bulk endpoints, making it straightforward to integrate into any backend or automation pipeline alongside ConvertAPI.
How accurate is BillionVerify's disposable email detection?
BillionVerify maintains a continuously updated list of known disposable and temporary email providers, providing high accuracy for flagging throwaway addresses before they enter your data pipeline.
Can I verify emails in bulk rather than one at a time?
Yes. The bulk API endpoint accepts large arrays of addresses and returns results efficiently, making it practical for high-volume document processing workflows built around ConvertAPI.
What verification result fields does BillionVerify return?
BillionVerify returns a verdict (valid, invalid, risky, catch-all), along with sub-checks for syntax, DNS, disposable detection, and role-address status — giving your pipeline precise control over how to handle each address.
Verify emails in Convertapi
Create a free account, grab your API key, and stop bounces before they happen.
Get started free