Form to meeting: Google Calendar, Zoom, Gmail & Slack booking automation
Pull contacts, verify each address with BillionVerify, and continue to Slack — 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 Slack 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
- 1Google Forms Webhook1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 2Merge Form Data1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 3Workflow Configuration1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 4Extract Booking Details1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Check Calendar Availability1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Is Time Slot Available?1Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 7Create Calendar Event1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 8Verify 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.
- 9Create Zoom Meeting1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 10IF deliverable 2Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 11Verify 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.
- 12Send Unavailable Email1Send· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 13IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 14Send Confirmation Email1Send· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 15Notify Teammate on Slack1Source· 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 Slack send or sync.
- Protecting Slack deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Slack?
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