🎬 Introducing BillionVerify Video Tutorials: short guides to verifying emails, free tools, and cleaning leads.Watch videos
← All Developer Tools Workflows
BillionVerifyAuthentica

Register users and authenticate with magic links using Google Sheets

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

The workflow

BillionVerify — verification sits right before the send.

+13
n8n steps
+18
n8n steps

Node by node

  1. 1
    On form registerTrigger· n8n

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

  2. 2
    On form loginTrigger· n8n

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

  3. 3
    AuthSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  4. 4
    ProfileSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  5. 5
    Create password and tokenSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  6. 6
    Check username/passwordSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  7. 7
    If has tokenLogic· n8n

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

  8. 8
    Check sid cookies headerSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  9. 9
    Append or update row in sheetSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  10. 10
    If login successLogic· n8n

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

  11. 11
    Search by tokenSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  12. 12
    Invalid tokenSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  13. 13
    Search sidSource· n8n

    Provides or transforms the contact data flowing through the workflow.

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

  15. 15
    If has token in DBLogic· n8n

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

  16. 16
    Redirect to login formSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  17. 17
    If token validLogic· n8n

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

  18. 18
    If has data with sidLogic· n8n

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

  19. 19
    IF deliverableLogic· n8n

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

  20. 20
    Redirect to auth urlSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  21. 21
    Generate tokenSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  22. 22
    Prepare sidSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  23. 23
    Redirect to login form1Source· n8n

    Provides or transforms the contact data flowing through the workflow.

  24. 24
    Prepare htmlSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  25. 25
    Redirect to loginSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  26. 26
    Send username/passwordSend· n8n

    Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.

  27. 27
    Add token to DBSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  28. 28
    Redirect to profile and set cookiesSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  29. 29
    Update sidSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  30. 30
    Show profile pageSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  31. 31
    Notice register successSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  32. 32
    Redirect to auth with new tokenSource· 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-authentica.json35 KB · n8n workflow

When to use this

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

FAQ

Why verify before sending in Authentica?

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