Waterfall email enrichment

Finds the best work email for a lead by chaining data providers in a fixed order and stopping at the first confident result — the "waterfall" pattern. No single provider wins on both coverage and accuracy, so chaining them gets you the coverage of all at the accuracy of your best one, and (because both providers here charge nothing on a miss) you only pay where an email actually lands.

How it works: 1. Apollo (People Enrichment) runs first and returns firmographics + a work email. If Apollo returns a real, non-placeholder email with email_status = "verified", that is the confident match and the chain stops. 2. Only if Apollo did not land a confident email, Hunter (Email Finder) runs as the fallback. Its result counts as confident when the score is high (>= 90) and the domain is not accept-all (catch-all). Hunter's finder verifies each email it returns, so no separate verify step is needed. 3. The workflow assembles one enriched record (email, status, which provider it came from, plus title / seniority / LinkedIn / industry / headcount) and displays it. If nothing confident was found it flags the lead for manual review.

Strictness is deliberately high — for cold outreach a wrong address is worse than a missing one. Tune the two gates (Apollo "verified", Hunter score >= 90 and not accept-all) to trade coverage for quality.

This template ships with a single example lead (Patrick Collison at Stripe) so it runs the moment Apollo and Hunter are connected. To make it your own: - Replace the five example inputs at the top (firstName / lastName / fullName / companyName / companyDomain). - To run it continuously, put it on a schedule and pull the leads yourself: list your Google Sheet or Airtable "leads" table, loop the waterfall over the rows, skip any already enriched, and write the enriched record back to each. (New-row triggers deliver no row data — they only wake the run — so a schedule that lists and skips already-done rows is simpler and equivalent; the "Airtable lead enrichment (waterfall)" template is this exact productionization.) Pace calls with a short Wait to stay under provider rate limits (a provider error aborts the run, so keep batches small). - Extend the chain by inserting cheaper providers before Hunter (Icypeas, Prospeo, Dropcontact) and, for a stricter finish, a standalone email verifier and a catch-all resolver. The chain logic stays identical; only the tiers change.