BillionVerifyDeepl

Translate documents to multiple languages with Google Drive and DeepL

Pull contacts, verify each address with BillionVerify, and continue to DeepL — 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 DeepL step removes that risk automatically — only deliverable addresses continue, the rest are flagged.

The workflow

BillionVerify — verification sits right before the send.

n8n steps

Verify Email (BillionVerify) 2

+23

n8n steps

Verify Email (BillionVerify)

n8n steps

Node by node

1
Google Drive TriggerTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
2
Error HandlerSource· n8n
Provides or transforms the contact data flowing through the workflow.
3
Merge ConfigurationSource· n8n
Provides or transforms the contact data flowing through the workflow.
4
Configuration (Edit Here)Source· n8n
Provides or transforms the contact data flowing through the workflow.
5
Verify 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.
6
Detect File FormatLogic· n8n
Routes items based on the workflow logic.
7
IF deliverable 2Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
8
Download PDFSource· n8n
Provides or transforms the contact data flowing through the workflow.
9
Download DOCXSource· n8n
Provides or transforms the contact data flowing through the workflow.
10
Download TXTSource· n8n
Provides or transforms the contact data flowing through the workflow.
11
Download MarkdownSource· n8n
Provides or transforms the contact data flowing through the workflow.
12
Send Error NotificationSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
13
Extract Text from PDFSource· n8n
Provides or transforms the contact data flowing through the workflow.
14
Extract Text from DOCXSource· n8n
Provides or transforms the contact data flowing through the workflow.
15
Read TXT FileSource· n8n
Provides or transforms the contact data flowing through the workflow.
16
Read Markdown FileSource· n8n
Provides or transforms the contact data flowing through the workflow.
17
Format Text DataSource· n8n
Provides or transforms the contact data flowing through the workflow.
18
Split by LanguageSource· n8n
Provides or transforms the contact data flowing through the workflow.
19
Translate a languageSource· n8n
Provides or transforms the contact data flowing through the workflow.
20
Generate FilenameSource· n8n
Provides or transforms the contact data flowing through the workflow.
21
Code in JavaScriptSource· n8n
Provides or transforms the contact data flowing through the workflow.
22
Create Translated FileSource· n8n
Provides or transforms the contact data flowing through the workflow.
23
Save to Google DriveSource· n8n
Provides or transforms the contact data flowing through the workflow.
24
Check if Notion EnabledLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
25
Record in NotionSource· n8n
Provides or transforms the contact data flowing through the workflow.
26
Merge ResultsSource· n8n
Provides or transforms the contact data flowing through the workflow.
27
Aggregate TranslationsSource· n8n
Provides or transforms the contact data flowing through the workflow.
28
Prepare NotificationSource· n8n
Provides or transforms the contact data flowing through the workflow.
29
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.
30
IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
31
Send Gmail NotificationSend· 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-deepl.json35 KB · n8n workflow

Download

When to use this

Cleaning a list before a DeepL send or sync.
Protecting DeepL 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 DeepL?

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