Verify emails before sending cold emails (Google Sheets → Gmail)
Send personalized cold emails from a Google Sheet through Gmail — but verify every address first so invalid and risky contacts never get a send.
Why verify before the send
Cold email lists are full of typos, stale addresses, catch-all domains, and spam traps. Sending to them spikes your bounce rate, burns your sending domain reputation, and lands future emails in spam. A single verification step before the send removes that risk: only deliverable addresses get emailed, the rest are flagged for review.
The workflow
Google Sheets → BillionVerify → Gmail — verification sits right before the send.
Node by node
- 1Schedule TriggerTrigger· n8n
Runs the workflow on a schedule (e.g. every weekday at 9am) so a batch of new contacts is processed automatically. Swap for a Manual Trigger while you test.
- 2Get rowsSource· google-sheets
Reads contact rows from your prospect sheet. Map the email column and optionally filter to rows where a "status" column is still empty so each contact is processed once.
- 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.
- 5Send emailSend· gmail
Only reached for deliverable addresses. Sends the personalized cold email via Gmail. Because every recipient was verified, bounces stay near zero.
- 6Mark as invalidLogic· google-sheets
For the false branch: write the verification status back to the sheet so the address is excluded next run and your list gets cleaner over time.
When to use this
- Cold outreach agencies cleaning scraped or purchased lists before the first touch.
- Founders running personalized outbound from a spreadsheet who cannot afford to burn their domain.
- Sales teams that enrich leads, then want a hard gate so reps never email a dead address.
FAQ
Does this verify in real time or in bulk?
Each row is verified in real time as the workflow processes it. For very large lists, switch the BillionVerify node to the bulk operation (up to 50 per call) or use the file verification API.
What happens to risky or catch-all addresses?
They are routed to the false branch by the IF node and written back to your sheet instead of being emailed. You decide whether to retry, review, or drop them.
Will this protect my sender reputation?
Yes. Bounces are the single biggest reputation killer for cold email. Verifying before every send keeps your bounce rate low, which keeps your domain trusted.
Add verification to your workflow
Create a free account, grab your API key, and stop bounces before they happen.
Get started free