Automated weekly product promotion emails for e-commerce with Algolia and Gmail
Pull contacts, verify each address with BillionVerify, and continue to Algolia — 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 Algolia 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 sundays 8.00 amTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2Test trigger for low-code branchTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 3Request products from AlgoliaSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4What day are we ?Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Date range generator (low code)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Extract Discounted ProductsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7Sunday ?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 8Keep only useful product dataSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 9Output date of todaySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 10Find last Monday's dateSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 11Put back all hits in one clean arraySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Clean Promo start dateSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 13Find last Sunday's dateSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 14Merge data for newsletterSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 15Calculate end of rangeSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 16Aggregate data for NewsletterSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17Clean Promo end dateSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 18Newsletter Generation (HTML Format)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 19Output Promo Validity Date RangeSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 20Get row(s) in sheetSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 21Verify 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.
- 22IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 23Send newsletterSend· 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.
When to use this
- Cleaning a list before a Algolia send or sync.
- Protecting Algolia deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Algolia?
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