Generate daily tech, manga & movies newsletter from RSS feeds with Brevo
Pull contacts, verify each address with BillionVerify, and continue to Brevo — 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 Brevo 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
- 1Schedule TriggerTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2Category RssSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 3Split Out2Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 4Rss databaseSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5SwitchLogic· n8n
Routes items based on the workflow logic.
- 6Loop Over Items3Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 7Loop Over Items4Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 8Loop Over Items5Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 9Code in Python (Beta)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 10RSS Read1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 11Code in Python (Beta)1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 12RSS Read2Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 13Code in Python (Beta)2Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 14RSS Read3Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 15MangaSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 16MovieSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17Jeu videoSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 18MergeSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 19AggregateSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 20HTML TemplateSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 21Mail CampaignSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 22Verify 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.
- 23IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 24Send a MailSend· 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 Brevo send or sync.
- Protecting Brevo deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Brevo?
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