BillionVerifyAutopilot

Verify emails before sending in Ortto (Autopilot)

Pull contacts from your list or CRM, verify each address, and send through Ortto (Autopilot) — only to addresses that are deliverable.

Get a free API key Install the n8n node

Why verify before the send

Automation journeys repeat sends, so one bad address bounces again and again until removed. A single verification step before the send removes that risk: only deliverable addresses are emailed, and invalid, risky, disposable, and catch-all addresses are filtered out automatically.

The workflow

BillionVerify → Autopilot — verification sits right before the send.

n8n steps

Verify Email

IF deliverable

Trigger Ortto (Autopilot) send

Flag invalid

Node by node

1
Schedule TriggerTrigger· n8n
Runs the workflow on a cadence so each new batch of contacts is processed automatically.
2
Get contactsSource· n8n
Reads the contacts to email — from a sheet, CRM, database, or webhook. Map the column that holds the email address.
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
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
Trigger Ortto (Autopilot) sendSend· autopilot
Starts the Ortto (Autopilot) automation for deliverable contacts only.
6
Flag invalidLogic· n8n
For the false branch: record the verification status so invalid addresses are excluded next run and your list keeps getting cleaner.

When to use this

Cleaning a list before a Ortto (Autopilot) campaign or automation.
Protecting Ortto (Autopilot) deliverability and sender reputation.
Keeping bounce rates low so Ortto (Autopilot) never throttles your sending.

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 Ortto (Autopilot)?

Automation journeys repeat sends, so one bad address bounces again and again until removed. Verifying first keeps your bounce rate low, which protects your reputation and your results.

Does this verify in real time or in bulk?

Each contact is verified in real time as the workflow runs. For large lists, use the BillionVerify bulk operation (up to 50 per call) or the file verification API.

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