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.
Node by node
- 1On form registerTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2On form loginTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 3AuthSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4ProfileSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Create password and tokenSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Check username/passwordSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7If has tokenLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 8Check sid cookies headerSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 9Append or update row in sheetSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 10If login successLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 11Search by tokenSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Invalid tokenSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 13Search sidSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 14Verify 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.
- 15If has token in DBLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 16Redirect to login formSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17If token validLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 18If has data with sidLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 19IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 20Redirect to auth urlSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 21Generate tokenSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 22Prepare sidSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 23Redirect to login form1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 24Prepare htmlSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 25Redirect to loginSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 26Send username/passwordSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 27Add token to DBSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 28Redirect to profile and set cookiesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 29Update sidSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 30Show profile pageSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 31Notice register successSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 32Redirect 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.
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