📍 Introducing MapLeads: Turn Google Maps, Bing Maps & Apple Maps into your lead list.Try MapLeads
← All AI Workflows
BillionVerifyAlephant

Email weekly AI agent cost and token reports with Alephant and Gmail

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

The workflow

BillionVerify — verification sits right before the send.

+4
n8n steps
+2
n8n steps

Node by node

  1. 1
    Weekly Monday TriggerTrigger· n8n

    Starts the workflow — on a schedule, a webhook, or manually while you test.

  2. 2
    Fetch Alephant Usage SummarySource· n8n

    Provides or transforms the contact data flowing through the workflow.

  3. 3
    Set Email RecipientSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  4. 4
    Format Usage ReportSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  5. 5
    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.

  6. 6
    IF deliverableLogic· n8n

    Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.

  7. 7
    Send Usage Summary EmailSend· 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-alephant.json9 KB · n8n workflow

When to use this

  • Cleaning a list before a Alephant send or sync.
  • Protecting Alephant deliverability and sender reputation.
  • Keeping bounce rates low so your sending is never throttled.

FAQ

Why verify before sending in Alephant?

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