← LeadFlowLive demoFree CSV repairPricingWhat is in the packGet all 4 workflows — $49
shipped documentation · published unedited

Read the pack before you buy it

This is the documentation that ships inside the ZIP — the same README, the same start-here steps, the same troubleshooting page written from our own failed runs. Generated from the shipping files (sha256 9f5a9f816769) by make-docs.mjs, not retyped; the site build fails if these files change and this page does not.

Run the live demo (no install) Get the pack — $49 launch Clean a CSV free, no n8n

On this page

LeadFlow Automation Pack (n8n)START HERE — LeadFlow Automation PackDEMO.md — 2-minute walkthrough of LeadFlowINSTALL — running n8n for this packTROUBLESHOOTING — LeadFlow Automation Pack

LeadFlow Automation Pack (n8n)

Four ready-to-import n8n workflows for B2B lead generation — compliant by design (no LinkedIn scraping, no account bans) — plus a zero-setup demo that runs with no credentials.

What's inside

FilePurpose
workflows/00-quick-demo.jsonZero-setup demo: 6 messy rows → clean leads, patterns, drafts (no credentials, no network)
workflows/01-lead-import-csv.jsonCSV (your export, as-is) → normalize headers → dedupe by email → Google Sheets
workflows/02-webhook-lead-capture.jsonWebhook (any form) → Google Sheets
workflows/03-ai-email-drafter.jsonLeads → AI-personalized email drafts (DeepSeek) → Google Sheets
workflows/04-email-patterns.jsonLeads → generate candidate email patterns (FREE, no API) → Google Sheets

Requirements

Setup

  1. Prove it runs first: import workflows/00-quick-demo.json and Execute it — no credentials, nothing written. Then configure the rest.
  2. n8n → Workflows → Import from File → choose each JSON.
  3. In your Google Sheet create three tabs: Sheet1 (your leads), Drafts (03 writes here), Email Patterns (04 writes here). Output tabs are separate on purpose — re-running a workflow can never treat generated rows as fresh leads.
  4. Open each Google Sheets node → replace the placeholder spreadsheet (YOUR_GOOGLE_SHEET_ID) with your file, pick the tab listed above, then choose your Google Sheets credential.
  5. Workflow 03 → select your DeepSeek (Header Auth) credential.
  6. Save, then click Execute workflow (each workflow starts from a Manual Trigger; #02 starts from its Webhook).
  7. Workflow 01's Load CSV node is preset to /home/node/.n8n-files/sample-data/leads-sample.csv, which the shipped Docker compose (setup/) mounts read-only - run it as imported. On npm or your own compose, n8n 2.x restricts file access to ~/.n8n-files (N8N_RESTRICT_FILE_ACCESS_TO): copy the CSV there or widen the variable, then point the node at your path. On n8n Cloud, file reads are limited to /home/node, so run 01 self-hosted and start Cloud users on 02/03/04.

Which CSV exports workflow 01 accepts

It renames the columns it recognises, so a Pipedrive / HubSpot / Mailchimp export runs without hand-editing the file:

Every other column (Phone, Owner, …) is appended to your sheet untouched. If no address column can be found, 01 stops with No email column found. Headers seen: … instead of writing rows with an empty email; a column called Email Status is deliberately not treated as an address.

Credentials needed

Limitations

Troubleshooting

Costs

Testing status (verified 2026-11-11)

START HERE — LeadFlow Automation Pack

What it is

4 importable n8n workflows for compliant B2B lead generation (no LinkedIn scraping, no account bans), plus a zero-setup demo that proves your n8n runs the pack before you connect anything.

60-second proof (no setup at all)

  1. Import workflows/00-quick-demo.json.
  2. Click Execute workflow on the node named Start - click Execute workflow.
  3. Open the last node, Summary - what just happened: 6 messy sample rows -> 3 clean leads, 15 email patterns, 3 drafted emails, 0 emails sent, 0 network calls, no credentials used.

It runs entirely in Code nodes: it reads no file, writes nothing, calls nothing. If this works, your n8n can run the pack. The other four workflows add Google Sheets as storage.

15-minute setup

  1. Have n8n ready — self-hosted Community is free (install guide: setup/INSTALL.md) or use n8n Cloud.
  2. In n8n: Workflows → Import from File → import the four workflow files (01–04) in workflows/.
  3. Create a Google Sheet with these headers on a tab named Sheet1: firstName, lastName, company, domain, email, topic. (Your CSV does not have to use those names — workflow 01 renames Email - Work, Work Email, First Name, Company Name and similar on the way in.) Add two more empty tabs: Drafts (workflow 03 output) and Email Patterns (workflow 04 output).
  4. Add a Google Sheets OAuth2 credential in n8n; in each Google Sheets node select your spreadsheet + the tab named above.
  5. (Workflow 03 only) Add a Header Auth credential: Name = Authorization, Value = Bearer <your DeepSeek key>.
  6. Open a workflow → click Execute workflow (01/03/04 start from a Manual Trigger, 02 from its Webhook).

Try it with the sample data

Requirements

Limitations

Docs

Support & license

DEMO.md — 2-minute walkthrough of LeadFlow

Prereqs

Script

  1. 00 Zero-setup demo: import 00-quick-demo.json, Execute → summary shows 6 messy rows → 3 clean leads, 15 patterns, 3 drafts, 0 sent, no credentials. Do this before connecting anything (no prereqs needed).
  2. 01 CSV import: import 01-*.json, set Load CSV path to the sample, select your sheet, Execute → leads appear (deduped).
  3. 02 Webhook: activate 02-*.json, POST {firstName,lastName,company,email} to the webhook URL → row appended.
  4. 03 AI email: Execute on leads → personalized drafts written to a sheet. (Verified output: 'Hi Jane — I came across Acme Studio ...')
  5. 04 Patterns: Execute → candidate emails (jane.doe@, janedoe@, j.doe@, jdoe@, jane@).

Verified expected outputs (2026-11-11)

INSTALL — running n8n for this pack

You need a working n8n instance. Any of these routes works; pick one.

Route A — n8n Cloud (fastest, no server)

  1. Create an account at n8n.cloud and open your instance.
  2. Continue with START-HERE.md (../START-HERE.md).

Route B — npm (local, no Docker)

  1. npm install -g n8n
  2. n8n start
  3. Open http://127.0.0.1:5678 (local only).

Notes: default DB is SQLite in ~/.n8n. Requires Node.js 20+.

  1. Install Docker Desktop (or Docker Engine on Linux/WSL2).
  2. In this setup/ folder: copy .env.example to .env and set N8N_ENCRYPTION_KEY to any long random string (keep it — it decrypts your stored credentials).
  3. docker compose up -d
  4. Open http://127.0.0.1:5678.

Optional in .env: GENERIC_TIMEZONE (default UTC).

The compose file already mounts this pack's sample-data/ folder read-only at /home/node/.n8n-files/sample-data - inside the folder n8n 2.x allows file nodes to read by default (N8N_RESTRICT_FILE_ACCESS_TO defaults to ~/.n8n-files). So workflow 01 reads its preset path without extra setup or env changes. Keep the compose file in setup/ (the mount path is relative to it). For Route B (npm), copy sample-data/leads-sample.csv into ~/.n8n-files/ instead.

Security (all routes)

After n8n is running

TROUBLESHOOTING — LeadFlow Automation Pack

Every item below was hit (and fixed) during our own end-to-end testing. Check here before emailing support.

1. "Could not find the sheet" / no rows appear

2. Credential errors on Google Sheets nodes

3. Workflow 03 returns HTTP 401 from api.deepseek.com

4. Workflow 01 can't read the CSV (ENOENT, or "Access to the file is not allowed")

Two different causes, same node - check which error you get.

"Access to the file is not allowed." (n8n 2.x, the default)

"ENOENT: no such file or directory"

5. Import fails / workflow looks empty

6. Workflow 02 webhook does nothing

7. Workflow 04 emails bounce

8. Re-running 03 or 04 fills my leads tab with junk rows

9. I imported the same CSV twice and my leads tab now has duplicates

10. My export says "Email - Work" / "Work Email" — does workflow 01 understand it?

Yes, no editing needed. 01 renames the columns it recognises to the ones the rest of the workflow uses:

Everything else (Phone, Owner, custom fields) is appended to the sheet as-is, so nothing is lost. If the run stops with No email column found. Headers seen: …, the list it prints is your file's real header row: rename the address column to email (or one of the names above) and run again. A column named Email Status / Email Valid is deliberately not used as an address.

11. Names arrive as ???? or "é" instead of Đorđe / François

The characters were destroyed before workflow 01 saw them, or they were written by Excel in an encoding nobody asked for. The two shapes have different answers.

Shape A — the cell holds ???? or ?or?e. Excel on a Serbian, Polish, Czech or Hungarian Windows writes CSV in Windows-1250 by default. n8n's Extract from File node decodes every CSV as UTF-8, so each byte above 0x7F that is not valid UTF-8 becomes a replacement character and the name is gone at that point - not lost later in the sheet.

Workflow 01 therefore carries a Decode CSV bytes node ahead of the parser. It reads the raw bytes and picks the first encoding that is provably correct, in this order:

  1. BOM - a UTF-8 or UTF-16 byte-order mark settles it, and the BOM itself is stripped.
  2. Strict UTF-8 - the file decodes cleanly, so it is UTF-8; nothing is rewritten.
  3. Windows-1250 - strict UTF-8 failed, so the bytes are read with the 1250 table (the one Excel used for those locales).

The node rewrites the file as UTF-8 and records the choice in encoding_used, so the CSV parser downstream only ever sees valid UTF-8. Check that field on the node's output if you want to know which route your file took. It does not guess between 1250 and 1252 by "most accented letters": a wrong guess silently renames people.

If the cell already shows ? after the Decode node, the bytes were replaced before the file reached n8n - by a previous save in a text editor, by a mail gateway, or by an export that was already damaged. No decoder can restore a byte that was replaced; the honest fix is to re-export from the source system. This is the one failure the pack does not fix, and it is stated in README's Limitations on purpose.

Shape B — the cell holds François or KováÄ. That is valid UTF-8 that some earlier tool decoded with a single-byte encoding and saved again. Because the text *is* valid UTF-8, the Decode node correctly leaves it alone. The free browser tool at the LeadFlow site reverses this shape cell by cell (it rebuilds the bytes and checks that the result is strict UTF-8), a file at a time; the pack's workflow 01 does not, so repair those rows before import or hand the file over as described on the site.

UTF-16 exports. Excel's "Unicode Text (*.txt)" and some CRM exports are UTF-16. Extract from File decodes UTF-8 only, so those arrive full of null bytes and the header is unrecognised. Save as CSV UTF-8 instead, or convert once with your spreadsheet's "Save As -> CSV UTF-8 (Comma delimited)".

Still stuck?

Reply to your purchase email with: n8n version, the failing workflow number, and the exact error text. Refund window and terms are in LICENSE.txt.

What this page is not: it is not the product. The ZIP contains the four importable workflow JSON files, the zero-setup demo workflow, the sample CSV, a Docker compose that mounts it correctly, the commercial-use license — and these documents. See what is in the pack →
Honest limits, repeated here: email patterns are candidates, not verified addresses, and you confirm each one before sending. Workflow 03 writes drafts to a sheet; it never sends email. n8n must be installed, and Google Sheets needs your own Google account.