The unglamorous part of a lead list: an export with headers like E-MAIL or Last-Name , the same person twice under two spellings, and half the addresses missing. Import one of these JSON files into n8n and press Execute workflow. No credentials, no HTTP requests, no data leaving your instance. These are the same workflows that ship inside the pack — nothing here is a crippled demo.
The same engine runs in your browser: paste a CSV or pick a file and get a cleaned CSV, a patterns CSV, and a report naming every rejected row — no upload, no account, nothing leaves the tab.
The dedupe workflow above is one design decision: what makes two rows the same person. The dedupe page prints the exact Code node, the run it did on a 12-row export (3 merged, 2 rejected with a reason) and the duplicates an email key cannot catch.
Before you judge any of it, the pack publishes one unedited run on a real export: the messy input, the cleaned file and the report that names every rejected row - 12 rows in, 7 usable leads, 5 removed with a reason each.
The free tier stops at “the file is clean”. The pack ($49 launch, 14-day refund on request) is for when the clean file has to become a pipeline someone runs every week:
If the free workflows got you most of the way, this is the same button the home page carries, at the same price. The receipt page hands you the ZIP immediately — no email round-trip, no account. The charge comes from dragana.karans@gmail.com; questions and refunds go to perun.intelligence@gmail.com.
Honest limits: email patterns are candidates, not verified addresses — you confirm each one before sending. Nothing here scrapes, buys lists, or sends mail on its own. Quoted fields with embedded line breaks are not handled. Formatting is cleaned; deliverability is not checked.
Free workflows are also published at github.com/fejzadenis/n8n-lead-toolkit · v1.0.0 release: the same 3 workflows as files · LeadFlow home