Waterfall Enrichment at Scale (Bridge to Lead Databases)
How to sequence multiple B2B data providers inside Clay or TexAu so every contact exits enrichment with a verified email and clean firmographic data, without manual re-runs or CSV hand-offs between tools.
Integration Context
Why a single provider leaves up to 40% of your list unenriched
A single B2B data provider covers roughly 60 to 75% of a given ICP list. Up to 40% of contacts exit enrichment with no verified email, no firmographic data, and no chance of a reply.
A waterfall fixes this: Clay or TexAu queries Provider 1 for each contact, falls to Provider 2 on no match, then Provider 3, stopping at the first verified result. Credits are consumed only when a provider returns a match.
Clay and TexAu both access 150+ providers via stop-on-first-match billing with native push to Instantly and Smartlead. Webhooks and HTTP API require TexAu Teams ($499/mo annual) or Clay's higher-tier plans.
How It Works
The waterfall enrichment integration flow, step by step
| Step | What happens | Tool | Method |
|---|---|---|---|
| 1 | Contact list enters enrichment orchestrator with name + company domain | Clay / TexAu | CSV import, CRM sync, or webhook trigger |
| 2 | Provider 1 queried for verified email and firmographics | Apollo / ZoomInfo / Cognism | Native provider integration via credits |
| 3 | If no match: fallback to Provider 2, then Provider 3, stop on first verified result | Findymail / Hunter / Lusha / UpLead | Waterfall fallback logic in Clay / TexAu |
| 4 | Email verification runs on every returned address before it advances | Clay built-in / Findymail / TexAu built-in | Automatic post-enrichment step |
| 5 | Verified, enriched records pushed to sending platform or CRM | Instantly / Smartlead / HubSpot / Salesforce | Native push or Make/Zapier connector |
Clay's native push to Instantly and Smartlead requires the Starter plan ($134/mo annual); two-way CRM sync requires a higher tier. TexAu webhooks require the Teams plan ($499/mo annual); Make/Zapier connectors work at any plan level.
Setup
How to configure waterfall enrichment in Clay or TexAu: 5 steps
- Step 1: Select your provider sequence based on ICP geography
Sequence providers by coverage strength for your ICP before configuring any columns: Apollo and ZoomInfo for North America, Cognism for EMEA phone-verified contacts, Findymail and Hunter as tier 2 fallbacks, UpLead and RocketReach as tier 3. A mismatch between your ICP geography and provider order means spending credits on weak coverage first.
- Step 2: Configure waterfall columns with stop-on-first-match logic
In Clay, create one enrichment column per provider and set each to run only if the previous column returned empty; name columns with a provider prefix (apollo_email, findymail_email) for traceability. In TexAu, set the provider order in the enrichment job settings and add a result source column to identify which provider returned each match.
- Step 3: Add email verification immediately after enrichment
Add a verification column running SMTP validation, catch-all detection, and disposable filtering on every returned address before it advances. Clay's built-in verification handles this automatically; add Findymail as a second-pass layer using its REST API if catch-all bounce risk is a concern.
- Step 4: Map output fields to your sending platform's required format
Confirm enrichment output field names match exactly the column headers your sending platform expects before pushing. In Clay, standard fields map automatically in the native Instantly/Smartlead integration; custom variables require manual mapping in the integration settings.
- Step 5: Schedule recurring runs and configure a fallback route for unmatched contacts
Set run frequency to match your signal cadence: daily for job-change-triggered lists, weekly for static ICP enrichment. Route all zero-match contacts to an "enrichment failed" segment for LinkedIn follow-up or manual review rather than discarding them.
Pushing enrichment output directly to a cold email sequence without a verification gate is the most common cause of bounce spikes. A batch with 15% catch-all addresses can push bounce rate above the 2% threshold that triggers inbox placement penalties across your entire sending domain.
Provider Layers
Orchestrators and providers by waterfall tier: Clay, TexAu, and 9 data sources
The orchestration layer (Clay or TexAu) manages provider sequencing, stop-on-first-match logic, verification, and push to your sending platform. The provider layer supplies the contact data at each tier.
A waterfall beyond three providers returns diminishing fill rates. Build a three-tier sequence, measure fill rate after the first batch, and add a fourth provider only if your tier-three fallback is still matching above 10%.
When It Breaks
4 waterfall failure points and their fixes
Common Questions
4 questions operators ask before running waterfall enrichment at scale
No. Clay accesses 150+ providers through its credits model with no separate subscriptions required. Some providers have usage limits or add-on pricing at higher volumes; verify at clay.com/pricing before estimating cost at scale.
TexAu cites waterfall fill rates improving from 60% on a single provider to 98%+ with stop-on-first-match logic. The actual gain depends on ICP: EMEA and niche verticals see the largest improvement; broad US Fortune 5000 lists see the smallest.
Both Clay and TexAu support phone waterfall enrichment, but phone credits cost 5 to 20 times more per record than email credits. Run phone waterfalls only on your highest-priority ICP segments; for EMEA mobile numbers, use Cognism Diamond Data as tier 1.
Confirm: result source populated, verification passing (no catch-all, no invalid format), required personalization fields filled, contact not already active in a live sequence, and batch volume within your daily send cap for the target campaign.
Waterfall configured? Build the full activation bridge to your sending platform.
The Clay to Instantly/Smartlead Activation guide covers the exact steps to connect enriched records from Clay into a live campaign, including field mapping, deduplication, and campaign ID configuration.
🔒 Affiliate links. We may earn a commission. Learn more