Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
Pull contacts, verify each address with BillionVerify, and continue to Reply — 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 Reply 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
- 1OpenAI Chat ModelSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 2OpenAI Chat Model2Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 3New EmailTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 4Structured OutputSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Structured Output1Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 6When clicking ‘Execute workflow’Trigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 7Structured Output ParserSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 8GPT-5-miniSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 9Test Emails (to fill memory)Source· n8n
Provides or transforms the contact data flowing through the workflow.
- 10Email to processSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 11Test Emails 2nd batchSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Fetch approved classification examplesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 13AI ClassifierSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 14Fetch approved email examplesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 15Set PromptSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 16AI Email WriterSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 17Human reviewSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 18Human responseLogic· n8n
Routes items based on the workflow logic.
- 19Is test run?Logic· n8n
Routes items based on the workflow logic.
- 20No ActionSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 21Set (edited) promptSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 22Verify 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.
- 23Is bug of feature request?Logic· n8n
Routes items based on the workflow logic.
- 24Email ProcessedSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 25IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 26AI AgentSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 27Reply to threadSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 28Create an issueSource· 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 Reply send or sync.
- Protecting Reply deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Reply?
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