BillionVerifyMicrosoft Outlook

Automatic Microsoft Outlook attachment storage to OneDrive with Excel logging

Pull contacts, verify each address with BillionVerify, and continue to Microsoft Outlook — 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 Microsoft Outlook 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)

n8n steps

Verify Email (BillionVerify) 2

n8n steps

Node by node

1
On Mail ReceivedTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
2
Get Message IDSource· n8n
Provides or transforms the contact data flowing through the workflow.
3
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.
4
IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
5
Get AttachmentsSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
6
Loop Over ItemsSource· n8n
Provides or transforms the contact data flowing through the workflow.
7
Notify UserSource· n8n
Provides or transforms the contact data flowing through the workflow.
8
Get Folder IDSource· n8n
Provides or transforms the contact data flowing through the workflow.
9
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.
10
IF deliverable 2Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
11
Download AttachmentSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
12
Upload to OneDriveSource· n8n
Provides or transforms the contact data flowing through the workflow.
13
Set FilenameSource· n8n
Provides or transforms the contact data flowing through the workflow.
14
Append to Excel LogSource· n8n
Provides or transforms the contact data flowing through the workflow.

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-microsoft-outlook.json14 KB · n8n workflow

Download

When to use this

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

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