B2B lead scraping & email verification
n8n-native prospecting pipeline that reads targeting inputs from Google Sheets, builds Apollo searches, scrapes via Apify with dedupe and normalization, keeps only verified emails, and appends clean lists back to Sheets—with rate limits tuned for stability.
Results at a glance
Dynamic Apollo URL construction from sheet-driven criteria
Duplicate suppression and verified-email-only outputs
Rate limiting and field normalization baked into the graph
Challenge
Growth teams were exporting brittle CSVs from multiple tools, losing dedupe discipline, and burning slots on bad emails. They needed a repeatable graph that marketing could parameterize without engineering babysitting every pull.
What Habrig built
- Google Sheets as the control plane for titles, company filters, and batch sizing familiar to operators
- Scheduled or on-demand triggers pulling inputs, looping titles, and assembling crawler-ready payloads
- Apify-powered scraping nodes with JSON shaping before Apollo-specific enrichment steps
- Hard gates that drop unverified addresses and collapse duplicates prior to append operations
- Limiter nodes coordinated with third-party quotas to avoid bans or partial exports
- Append-only Sheet targets with schema validation so downstream CRM imports do not corrupt existing rows
Outcomes
- Cleaner lead files ready for CRM import or sequencer tools
- Less time reconciling “which sheet is canonical?” across reps
- Operational transparency via n8n execution history when a batch underfills expectations
Technology
frontend
Sheets-first UX for inputs and outputs; optional notifications when jobs finish
backend
n8n loops, HTTP tooling toward Apollo/Apify endpoints, and deterministic cleanup subgraphs
database
Google Sheets as the staging warehouse; optional downstream sync hooks left adapter-friendly
infrastructure
Hosted automation tier sized for nightly pulls with credential rotation support
monitoring
Row-count sanity checks, runtime alerts on repeated HTTP failures, and archived run logs
cicd
Workflow exports reviewed before credential swaps; test sheets isolated from production tabs
Execution detail
Product & frontend
- Google Sheets as the control plane for titles, company filters, and batch sizing familiar to operators
Backend & data
- Scheduled or on-demand triggers pulling inputs, looping titles, and assembling crawler-ready payloads
- Apify-powered scraping nodes with JSON shaping before Apollo-specific enrichment steps
- Hard gates that drop unverified addresses and collapse duplicates prior to append operations
Platform & delivery
- Limiter nodes coordinated with third-party quotas to avoid bans or partial exports
- Append-only Sheet targets with schema validation so downstream CRM imports do not corrupt existing rows
Gallery
Plan your next release
Tell us what shipped, what is at risk, and what success looks like. We will respond with a practical path.
Book a consultation