Pre-meeting email nurturing sequence with Cal.com and Gmail
Pull contacts, verify each address with BillionVerify, and continue to Cal.com — 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 Cal.com 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
- 1Cal.com TriggerTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2Extract prospectSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 3IfLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 4Calculate timeSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Switch: Days Until MeetingLogic· n8n
Routes items based on the workflow logic.
- 6Quick prep emailSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7Verify 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.
- 8Verify Email (BillionVerify) 5Verify· 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.
- 9Verify Email (BillionVerify) 4Verify· 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.
- 10IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 11IF deliverable 5Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 12IF deliverable 4Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 13Casual flexSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 14Casual flex 8+ daysSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 15Send itSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 16Wait 1 DaySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17Wait 1 Day1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 18Verify Email (BillionVerify) 2Verify· 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.
- 19Verify Email (BillionVerify) 6Verify· 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.
- 20IF deliverable 2Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 21IF deliverable 6Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 22Casual pressSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 23Casual press 8+daysSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 24Wait another daySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 25Wait another day 8+daysSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 26Verify Email (BillionVerify) 3Verify· 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.
- 27Verify Email (BillionVerify) 7Verify· 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.
- 28IF deliverable 3Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 29IF deliverable 7Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 30Casual knowledge flexSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 31Casual knowledge flex 8+daysSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 32WaitSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 33Wait1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 34Quick prep email (2)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 35Quick prep email2Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 36Verify Email (BillionVerify) 8Verify· 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.
- 37Verify Email (BillionVerify) 9Verify· 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.
- 38IF deliverable 8Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 39IF deliverable 9Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 40Quick prepSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 41Quick prep +8daysSend· 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 Cal.com send or sync.
- Protecting Cal.com deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Cal.com?
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