Monitor brand mentions with GPT-5 Nano, Brave Search, Gmail and Google Sheets
Pull contacts, verify each address with BillionVerify, and continue to Mention — 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 Mention 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
- 1Every DayTrigger· n8n
Starts the workflow — on a schedule, a webhook, or manually while you test.
- 2Set keyword and descriptionSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 3Check & Log to SheetSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 4Set ConfigSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 5MergeSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 6Split DorkySource· n8n
Provides or transforms the contact data flowing through the workflow.
- 7NewURL?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 8URL_Is_NOT_emptyLogic· n8n
Routes items based on the workflow logic.
- 95sSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 10Format EmailSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 11No New ResultsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 12Remove DuplicatesSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 13Loop SetupSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 14Verify 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.
- 15RelevancyVerificationSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 16Brave SearchSource· 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.
- 18FilterRelevantOnlyLogic· n8n
Routes items based on the workflow logic.
- 19Message a modelSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 20HasResult?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 21Send EmailSend· n8n
Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.
- 22AnyRelevantResults?Logic· n8n
Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.
- 23MergeOutput&InputSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 24Split ResultsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 25Continue LoopSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 26InsertSentRowsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 27No Relevant ResultsSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 28Extract DataSource· n8n
Provides or transforms the contact data flowing through the workflow.
- 29FilterBannedDomainsLogic· n8n
Routes items based on the workflow logic.
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 Mention send or sync.
- Protecting Mention deliverability and sender reputation.
- Keeping bounce rates low so your sending is never throttled.
FAQ
Why verify before sending in Mention?
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