Create AI newsletters with GPT-4o, human approval workflow, and SendGrid
Pull contacts, verify each address with BillionVerify, and continue to SendGrid — 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 SendGrid 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
- 1Newsletter Input FormTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2OpenAI GPT-4o ModelSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 3JSON Output ParserSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4Workflow ConfigurationSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5Store Form ResponsesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Generate Newsletter ContentSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7Convert Markdown to HTMLSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 8Verify 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.
- 9IF deliverableLogic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 10Send Approval EmailSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 11Wait for ApprovalSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Verify 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.
- 13IF deliverable 2Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 14Send Newsletter to SubscribersSend· 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 SendGrid send or sync.
- Protecting SendGrid deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in SendGrid?
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