Monitor Klaviyo list decay with Postgres logging and Gmail reports
Pull contacts, verify each address with BillionVerify, and continue to Klaviyo — only deliverable addresses get through.
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 Klaviyo step removes that risk automatically — only deliverable addresses continue, the rest are flagged.
The workflow
BillionVerify — verification sits right before the send.
Node by node
- 1Schedule: Daily 2AMTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2Error TriggerTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 3Set: Initialize RunSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4Prepare Error DataSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Get All ProfilesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Log Error to DBSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7Extract Profile ItemsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 8Verify 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.
- 9Score ProfilesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 10IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 11Log Profiles to DBSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Build Run SummarySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 13Is Critical?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 14Send Error AlertSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 15Insert Run SummarySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 16Suppress Critical in BatchesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17Build Email HTMLSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 18Verify Email (BillionVerify) 2Verify· 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.
- 19IF deliverable 2Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 20Send a messageSend· 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.
When to use this
- Cleaning a list before a Klaviyo send or sync.
- Protecting Klaviyo deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Klaviyo?
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