Auto-schedule demos for high-intent leads with Clearbit, Slack, and Calendly
Pull contacts, verify each address with BillionVerify, and continue to Clearbit — 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 Clearbit 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
- 1Lead Form WebhookSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 2Normalize Lead DataSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 3Enrich with ClearbitSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4Calculate Fit ScoreSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5High Intent Lead?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 6Create HubSpot ContactSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7Alert Sales (Standard)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 8Create HubSpot DealSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 9Get Calendly Event TypesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 10Prepare Availability ParamsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 11Get Available Demo SlotsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Format Demo SlotsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 13Alert Sales (High Intent)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 14Wait 10 MinutesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 15Log to Google SheetsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 16Webhook ResponseSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17Check Slack RepliesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 18No Response?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 19Verify 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.
- 20IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 21Send Fallback EmailSend· 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 Clearbit send or sync.
- Protecting Clearbit deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Clearbit?
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