BillionVerifyDrift

Track commodity portfolio drift with Google Sheets, Gemini AI and Gmail alerts

Pull contacts, verify each address with BillionVerify, and continue to Drift — only deliverable addresses get through.

Download n8n workflow (JSON)Install the n8n node

Why verify before the send

Sending to invalid, risky, catch-all, or disposable addresses spikes your bounce rate and erodes sender reputation. A verification gate before the Drift step removes that risk automatically — only deliverable addresses continue, the rest are flagged.

The workflow

BillionVerify — verification sits right before the send.

+20

n8n steps

Verify Email (BillionVerify)

n8n steps

Node by node

1
Daily Portfolio Rebalance CheckTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
2
Read HoldingsSource· n8n
Provides or transforms the contact data flowing through the workflow.
3
Workflow SettingsSource· n8n
Provides or transforms the contact data flowing through the workflow.
4
Synchronize InputsSource· n8n
Provides or transforms the contact data flowing through the workflow.
5
Prepare Portfolio ContextSource· n8n
Provides or transforms the contact data flowing through the workflow.
6
Validate Portfolio DataSource· n8n
Provides or transforms the contact data flowing through the workflow.
7
Check Validation StatusLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
8
Calculate Portfolio AllocationSource· n8n
Provides or transforms the contact data flowing through the workflow.
9
Prepare Validation Failure LogSource· n8n
Provides or transforms the contact data flowing through the workflow.
10
Detect Portfolio DriftSource· n8n
Provides or transforms the contact data flowing through the workflow.
11
Log Validation FailureSource· n8n
Provides or transforms the contact data flowing through the workflow.
12
Check Rebalance RequirementLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
13
Classify Alert SeveritySource· n8n
Provides or transforms the contact data flowing through the workflow.
14
Prepare No Action LogSource· n8n
Provides or transforms the contact data flowing through the workflow.
15
Build Alert PromptSource· n8n
Provides or transforms the contact data flowing through the workflow.
16
Log No ActionSource· n8n
Provides or transforms the contact data flowing through the workflow.
17
Generate Alert MessageSource· n8n
Provides or transforms the contact data flowing through the workflow.
18
Merge Alert DataSource· n8n
Provides or transforms the contact data flowing through the workflow.
19
Prepare Alert PayloadSource· n8n
Provides or transforms the contact data flowing through the workflow.
20
Log Sent AlertSource· n8n
Provides or transforms the contact data flowing through the workflow.
21
Verify Email (BillionVerify)Verify· billionverify
The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.
22
IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
23
Send Rebalance EmailSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.

Workflow JSON

Copy or download this workflow, then import it in n8n (Workflows → Import from File / Paste). Install the BillionVerify community node first, then add your API key credential.

verify-emails-in-drift.json37 KB · n8n workflow

Download

When to use this

Cleaning a list before a Drift send or sync.
Protecting Drift deliverability and sender reputation.
Keeping bounce rates low so your sending is never throttled.

Three ways to connect

n8n node

Install the BillionVerify community node and drop it into this workflow.

Integrately

1-Click connect BillionVerify with 1500+ apps, no code.

REST API

Call the verification API directly from any stack.

FAQ

Why verify before sending in Drift?

Verifying first keeps your bounce rate low, which protects your sender reputation and your results.

How do I import this workflow?

Download the JSON, then in n8n go to Workflows → Import from File (or paste it). Install the BillionVerify community node and add your API key credential.

What happens to risky or catch-all addresses?

They are routed to the false branch and excluded from the send. You decide whether to retry, review, or drop them.

Add verification to your workflow

Create a free account, grab your API key, and stop bounces before they happen.

Get started free