Verify emails before sending in lemlist
Pull contacts from your list or CRM, verify each address, and send through lemlist — only to addresses that are deliverable.
Why verify before the send
lemlist sequences send from your real mailboxes, where bounces quickly damage sender reputation. A single verification step before the send removes that risk: only deliverable addresses are emailed, and invalid, risky, disposable, and catch-all addresses are filtered out automatically.
The workflow
BillionVerify → Lemlist — verification sits right before the send.
Node by node
- 1Schedule TriggerTrigger· n8n
Runs the workflow on a cadence so each new batch of contacts is processed automatically.
- 2Get contactsSource· n8n
Reads the contacts to email — from a sheet, CRM, database, or webhook. Map the column that holds the email address.
- 3Verify EmailVerify· billionverify
The BillionVerify node, operation "Verify Email". Map its Email field to the address from the previous node. It returns status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, a confidence score, and the reason — all before anything is sent.
- 4IF deliverableLogic· n8n
Branches on the verification result. Condition: is_deliverable is true. The true branch continues to the send; the false branch skips the send and flags the contact.
- 5Add to lemlist campaignSend· lemlist
Adds only deliverable prospects to your lemlist campaign, keeping every sending mailbox healthy.
- 6Flag invalidLogic· n8n
For the false branch: record the verification status so invalid addresses are excluded next run and your list keeps getting cleaner.
When to use this
- Cleaning a list before a lemlist campaign or automation.
- Protecting lemlist deliverability and sender reputation.
- Keeping bounce rates low so lemlist never throttles your sending.
FAQ
Why verify before sending in lemlist?
lemlist sequences send from your real mailboxes, where bounces quickly damage sender reputation. Verifying first keeps your bounce rate low, which protects your reputation and your results.
Does this verify in real time or in bulk?
Each contact is verified in real time as the workflow runs. For large lists, use the BillionVerify bulk operation (up to 50 per call) or the file verification API.
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