PipedriveBillionVerifyGmail

Verify before CRM follow-up emails (CRM → Gmail)

Contacts due for a follow-up are pulled from your CRM, verified, and the deliverable ones receive the next email in the sequence via Gmail.

Get a free API key Install the n8n node

Why verify before the send

CRM data decays — people change jobs and addresses go dead. Continuing to email them quietly raises your bounce rate over time and erodes deliverability for everyone else in the sequence.

The workflow

Pipedrive → BillionVerify → Gmail — verification sits right before the send.

Schedule Trigger

IF deliverable

Node by node

1
Schedule TriggerTrigger· n8n
Runs the follow-up batch on a regular cadence.
2
Get due contactsSource· pipedrive
Pulls contacts whose next follow-up is due from your CRM.
3
Verify EmailVerify· billionverify
The BillionVerify node, operation "Verify Email". Map its Email field to the address from the previous node. It returns status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, a confidence score, and the reason — all before anything is sent.
4
IF deliverableLogic· n8n
Branches on the verification result. Condition: is_deliverable is true. The true branch continues to the send; the false branch skips the send and flags the contact.
5
Send follow-upSend· gmail
Sends the next sequence email via Gmail for deliverable contacts only.
6
Mark staleLogic· pipedrive
For the false branch: flag the contact as stale in the CRM so it stops receiving emails until re-validated.