Lead Enrichment & Verification
Checks which prospects are still trading, finds and verifies a real email for each, and re-queues the ones that fail.
The problem
A bought or scraped lead list is mostly noise. Businesses have closed, domains have lapsed, and a large share of the email addresses were guesses to begin with. Send to it as-is and you burn your sending domain's reputation on bounces before you ever reach the people who would have replied.
What we built
A pipeline that qualifies the list before anything is sent. Each lead is checked for a live website, then put through email discovery, then verification — and only rows that come out the other end with a verified address are marked ready. Everything else is flagged with the reason it failed rather than silently dropped.
How it works
n8n loops the pending rows one at a time. A HEAD request tests whether the domain still resolves, so dead businesses are flagged before any paid lookup is spent on them. Surviving leads go to Hunter.io for a domain search, then through Hunter's verifier. Both stages are rate-limited deliberately — a short pause between calls — so the pipeline stays inside API limits instead of tripping them and losing the batch.
The retry queue
Verification is not always decisive on the first attempt; addresses come back as unknown rather than valid or invalid. Those are written to a separate retry sheet that a scheduled job works through daily. It's the part that matters most in practice — without it, every ambiguous result is a lead quietly thrown away.