Predict deal close dates and update Salesforce with Groq and Google Sheets
Pull contacts, verify each address with BillionVerify, and continue to Close — 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 Close 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
- 1InsightsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 2Run ScheduleTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 3Set Lookback TimeframeSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4Fetch Historical Won DealsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Fetch Recent Active DealsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Process OpportunitiesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7Fetch Deal DetailsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 8Deal Task HistorySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 9Is Deal Valid & Active?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 10Calculate Deal Risk & VelocitySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 11AI Deal Timeline PredictorSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Parse AI OutputSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 13check confidence scoreLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 14Update Close DateSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 15Verify 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.
- 16Log Auto-Update SuccessSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 18alert for Manual reviewSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 19Log Pending ReviewSource· n8n
Provides or transforms the contact data flowing through the workflow.
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 Close send or sync.
- Protecting Close deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Close?
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