BillionVerify
Sign In
← All Cold Outreach Workflows
HubSpotBillionVerifyMicrosoft Outlook

Verify before sales outreach (HubSpot leads → Outlook)

New leads are pulled from HubSpot, verified, and the deliverable ones receive a first outreach email through Outlook.

Get a free API keyInstall the n8n node

Why verify before the send

Enriched and scraped lead data is noisy. Reps sending from a real Outlook mailbox can trash their personal sending reputation on a single bad batch. Verifying first protects both deliverability and rep productivity.

The workflow

HubSpot → BillionVerify → Microsoft Outlook — verification sits right before the send.

Schedule Trigger
hubspot
Get new leads
billionverify
Verify Email
IF deliverable
microsoft-outlook
Send outreach

Node by node

  1. 1
    Schedule TriggerTrigger· n8n

    Runs the outreach batch on a cadence (e.g. each morning).

  2. 2
    Get new leadsSource· hubspot

    Pulls leads from a HubSpot list or view that have not yet been contacted.

  3. 3
    Verify EmailVerify· billionverify

    The BillionVerify node, operation "Verify Email". Map its Email field to the address from the previous node. It returns status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, a confidence score, and the reason — all before anything is sent.

  4. 4
    IF deliverableLogic· n8n

    Branches on the verification result. Condition: is_deliverable is true. The true branch continues to the send; the false branch skips the send and flags the contact.

  5. 5
    Send outreachSend· microsoft-outlook

    Sends the first-touch email via Outlook for deliverable leads only.

When to use this

  • SDR teams running outbound from individual Outlook mailboxes.
  • Agencies protecting client domains during cold campaigns.
  • Founders doing personalized outreach who want zero hard bounces.

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 does a verified list matter for Outlook specifically?

Microsoft is aggressive about reputation. A spike in bounces can throttle or block your mailbox, so a verification gate is especially valuable here.

Can I add a follow-up sequence?

Yes. Branch the deliverable path into a multi-step sequence; the verification only needs to happen once, before the first send.

How are risky addresses handled?

They are excluded from the send and can be tagged in HubSpot for manual review or re-enrichment.

Add verification to your workflow

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

Get started free