Metabase email verification with BillionVerify
Metabase is an open-source analytics and business intelligence platform that lets teams explore data, build dashboards, and share insights without writing SQL. When Metabase surfaces customer data containing email addresses, verification ensures your analytics and exports reflect accurate, deliverable contact information.
Why verify before the send
Analytics dashboards and exports built on top of unverified email data produce misleading engagement metrics and unreliable segments. BillionVerify lets you audit and clean the email fields in your underlying data before they skew reports, feed marketing campaigns, or get exported to operational tools.
Ready-to-use n8n workflow
Import this workflow into n8n — it verifies every address with BillionVerify before Metabase sends, so only deliverable contacts are emailed. Install the BillionVerify community node first, then add your API key.
{
"name": "Verify emails before sending in Metabase + 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 Metabase contacts",
"message": "Replace this Gmail send with your Metabase 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 Metabase
Ready-to-use workflows that verify emails before Metabase sends.
How it works
- 1
Use n8n or the BillionVerify REST API to build a verification pipeline connected to your underlying data source.
- 2
Query Metabase or the connected database to extract email addresses that need verification or re-verification.
- 3
Send each address to BillionVerify and receive results covering deliverability, catch-all status, and disposable detection.
- 4
Write the verification results back to your database so they appear in Metabase reports and dashboards.
- 5
Schedule recurring verification runs to keep email quality data current as your contact base grows.
When to use this
Audit customer email quality before campaign exports
Before exporting a Metabase segment to a marketing tool, run the email column through BillionVerify to remove invalid, disposable, and role-based addresses, so campaigns launch against a clean audience.
Enrich analytics with email quality signals
Add a verified status column to your data warehouse so Metabase dashboards can surface email deliverability rates alongside other contact quality metrics, giving teams visibility into list health over time.
Trigger re-verification workflows for aging records
Use Metabase queries to identify contacts whose email was last verified more than six months ago, then trigger BillionVerify re-checks to keep quality data fresh and actionable.
FAQ
Can I see email verification results directly in a Metabase dashboard?
Yes. Once you write BillionVerify results back to your database as a column or separate table, Metabase can query and visualize them like any other data field — showing deliverability rates, invalid counts, and trends over time.
Does BillionVerify integrate directly with Metabase, or does it need middleware?
BillionVerify connects via its REST API, so you typically use n8n or a lightweight script to orchestrate data movement between your database, BillionVerify, and Metabase's underlying data source.
How often should I re-verify emails in my database?
Industry best practice is to re-verify contact emails every three to six months, since addresses change as people leave jobs or abandon inboxes, meaning an old valid result may no longer be accurate.
Can BillionVerify handle large exports from Metabase?
Yes. BillionVerify's bulk verification API is designed for large volumes, so you can verify tens of thousands of exported addresses in a single batch without performance issues.
Verify emails in Metabase
Create a free account, grab your API key, and stop bounces before they happen.
Get started free