n8n B2B Lead Generation Pipeline
Eleven n8n workflows that source leads from Google Maps, research each company with an LLM, verify contacts and run a four-touch email sequence with reply handling.
Source repositories
n8n workflows
Each diagram is drawn from the workflow’s own JSON. Download a file and import it in n8n (Workflows → Import from file), then attach your own credentials — every credential and instance ID has been removed.
01 — Sourcing (GMaps daily)
10 nodes · 10 connections
Download JSON
01 — Sourcing (GMaps daily)
10 nodes · 10 connections
- Trigger
- Code
- Logic
- HTTP
- Database
02 — Enrichment (every 10 min)
17 nodes · 17 connections
Download JSON
02 — Enrichment (every 10 min)
17 nodes · 17 connections
- Trigger
- Database
- Logic
- Code
- HTTP
02b — Qualification Gate
13 nodes · 16 connections
Download JSON
02b — Qualification Gate
13 nodes · 16 connections
- Trigger
- Database
- Logic
- Code
- HTTP
02c — Opportunity Research (70B)
12 nodes · 12 connections
Download JSON
02c — Opportunity Research (70B)
12 nodes · 12 connections
- Trigger
- Database
- Logic
- Code
- HTTP
03 — Contact Discovery + Email Verify
18 nodes · 19 connections
Download JSON
03 — Contact Discovery + Email Verify
18 nodes · 19 connections
- Trigger
- Database
- Logic
- Code
- HTTP
04a — Outreach Touch 1 (Day 0)
22 nodes · 23 connections
Download JSON
04a — Outreach Touch 1 (Day 0)
22 nodes · 23 connections
- Trigger
- Database
- Code
- Logic
- HTTP
- Messaging
04b — Outreach Touch 2 (Day +4)
14 nodes · 17 connections
Download JSON
04b — Outreach Touch 2 (Day +4)
14 nodes · 17 connections
- Trigger
- Database
- Logic
- Code
- HTTP
- Messaging
04c — Outreach Touch 3 (Day +9, secondary contact)
12 nodes · 14 connections
Download JSON
04c — Outreach Touch 3 (Day +9, secondary contact)
12 nodes · 14 connections
- Trigger
- Database
- Logic
- Code
- HTTP
- Messaging
04d — Outreach Touch 4 (Day +14, soft close)
7 nodes · 7 connections
Download JSON
04d — Outreach Touch 4 (Day +14, soft close)
7 nodes · 7 connections
- Trigger
- Database
- Logic
- Code
- Messaging
05 — Reply Handler
33 nodes · 35 connections
Download JSON
05 — Reply Handler
33 nodes · 35 connections
- Trigger
- Code
- HTTP
- Logic
- Database
- Messaging
06 — Booking to Brief (Telegram)
14 nodes · 13 connections
Download JSON
06 — Booking to Brief (Telegram)
14 nodes · 13 connections
- Trigger
- Code
- Database
- HTTP
- Messaging
- Logic
Project overview
A complete outbound system built from n8n workflows and PostgreSQL. Leads are sourced daily, enriched from their websites, filtered by an LLM qualification gate, and researched by a 70B model that finds the most painful manual workflow at each company. Outreach runs over 14 days, replies are drafted for human approval in Telegram, and a booked call produces a briefing.
What I built
- 01
Sourcing, enrichment, qualification and research run as separate scheduled workflows sharing one Postgres state machine.
- 02
Contact discovery finds the primary decision-maker and verifies the address before anything is sent.
- 03
Four outreach touches on days 0, 4, 9 and 14; the booking link appears only in the last one or after a reply shows interest.
- 04
A reply handler classifies responses and drafts answers that a human approves from Telegram before they go out.
Implementation notes
Each stage is its own workflow, so a failing scraper or model call stalls one stage without losing leads further down.
Runs on Groq (LLaMA 3.3 70B), Gmail OAuth, Telegram, Playwright and Reacher on a single self-hosted VPS.
Technology stack
- n8n
- PostgreSQL
- Groq
- LLaMA 3.3 70B
- Gmail
- Telegram
- Playwright
More open-source projects
Need a similar product?
Let’s discuss the workflow, website, or application you want to ship.