Scrape Google Maps with n8nCapture leads free, then automate everything
The clean way to build an n8n Google Maps pipeline: capture businesses with the free Vonsel Chrome extension, export CSV or JSON, then let n8n do the rest. No Places API, no custom scraper.
Integrations··8 min read
Key takeaways
n8n is a brilliant automation engine, but it needs clean input. Getting Google Maps data into it is the hard part, not the automating.
Skip the Places API and the custom scraper node: capture businesses with the free Vonsel extension, export CSV or JSON, and feed that file into n8n.
The extension is the means. The Vonsel dashboard (mapped CRM, review intelligence, AI email per business) is the end when you want the pipeline handled for you.
The real bottleneck
n8n is easy. Getting the data is not.
n8n is one of the best open source automation tools around. Drag a trigger, add a few nodes, and you can validate emails, push contacts to a CRM, and fire outreach sequences without writing much code. The problem was never the automation. The problem is the fuel.
Most tutorials tell you to wire up the Google Places API inside an HTTP Request node. That works, but it means an API key, billing enabled, a per-request cost, and a hard ceiling of roughly 120 results per query. Others tell you to build a headless browser scraper, which is fragile and breaks every time Google shifts its markup.
There is a far simpler path. Capture the businesses first with a free Chrome extension, export a file, then let n8n take over. No API key, no billing, no brittle scraper node. You separate the capture step from the automation step, and each one becomes trivial.
Start with the capture step
Grab the businesses from Google Maps in a couple of clicks, then export them for n8n. Free download. No trial, no credit card.
API keys or billing accounts needed to capture the leads
3
export formats ready for n8n: CSV, XLSX, and JSON
1
webhook is all n8n needs to ingest the exported file
Step by step
Capture in the browser, automate in n8n
Here is the full workflow, broken into the part you do once in the browser and the part n8n repeats for you.
1. Capture on Google Maps. Open Google Maps, run a search like "dentists in Madrid" or "roofers in Chicago", and click the Vonsel pop-up. The extension collects business name, address, phone, website, and more as you scroll the results. This is the same idea covered in our guide on using a Google Maps scraper Chrome extension.
2. Export a file. When the capture finishes, export it. For n8n, JSON is usually the cleanest choice because each business becomes an item, but CSV works everywhere. See the CSV, XLSX, and JSON export options to pick the right one.
3. Ingest into n8n. You have two common entry points. Trigger a workflow manually with a Read Binary File node pointed at the export, or set up a Webhook node and drop the file to it. From there, an HTTP Request node or a Spreadsheet File node parses the rows into items.
4. Automate the rest. Now you are in n8n's home turf. Split the items, run each business through email validation, deduplicate against your existing list, enrich the website, and push the clean contact into a CRM or an outreach tool.
Workflow map
A practical n8n Google Maps pipeline
Stage
Node in n8n
What it does
Ingest
Read Binary File / Webhook
Loads the Vonsel export (CSV or JSON) into the workflow
Parse
Spreadsheet File / Edit Fields
Turns rows into clean items with named fields
Deduplicate
Remove Duplicates
Drops businesses already in your database
Validate
HTTP Request
Checks emails and phone formats before outreach
Route
CRM node
Creates or updates the contact in your CRM
Act
Email / Messaging
Triggers a first-touch sequence per business
This is the same shape whether you send the data on to HubSpot, Airtable, or a cold email tool. The exported file is the constant. If you would rather avoid the API layer completely, see how to export Google Maps leads to any CRM without an API.
The reason this beats the Places API route is not just cost. It is control. You see exactly which businesses you captured, you filter them before they ever hit n8n, and you never worry about a quota or a scraper breaking mid-run. Clean input makes the automation boring, and boring automations are the ones that keep working.
Why capture separately
What a browser capture gives your workflow
No API, no billing
The Places API needs a key and an enabled billing account, and it caps results per query. A browser capture sidesteps all of it and stays free.
Filter before automating
Drop businesses without a website or without a phone before the file reaches n8n, so your workflow only runs on leads worth the effort.
Website enrichment
Vonsel can pull emails, phone numbers, and social profiles from each business website during capture, so n8n gets richer items to work with.
Reopen and add more
Come back to a previous capture, add another city or category, then export a single combined file. Your n8n workflow does not change.
Stable format
A clean CSV or JSON schema does not shift under you the way raw scraped HTML does, so your parse node keeps working month after month.
n8n is powerful, but it is still a build. You maintain the nodes, watch the runs, and fix the breakages. For a lot of teams that is the point, and for others it is overhead they would rather skip.
That is where the Vonsel dashboard comes in. The extension captures the businesses, but the dashboard is the destination: a mapped CRM where every lead lands on a real map, review intelligence that surfaces customer pain points, sales intelligence that scores who to call first, and email intelligence that drafts an AI email tailored to each business. It is the same end state your n8n pipeline is trying to reach, without the wiring.
Think of it as two roads to the same place. Build it yourself in n8n for maximum flexibility, or let the dashboard turn a raw capture into a value added, context rich database out of the box. For a side by side of the two mindsets, see n8n workflow vs the extension. And if you are weighing automation platforms, our Make.com Google Maps automation guide follows the exact same capture-then-automate pattern.
n8n automates the pipeline. The capture is what fills it.
A note on the Places API
Why the no-API path wins for most people
The Google Places API is a genuinely good product for developers who need programmatic lookups at scale, and if you already run a metered pipeline it may fit. But for a sales or agency team that just wants leads flowing into n8n, the setup cost, the per-request billing, and the result caps rarely pay off.
The browser capture gives you the same core fields, lets you eyeball the list, and hands n8n a file it can chew through instantly. For a broader look at the trade-off, read Chrome extension vs API scraping. Whichever route you take, the automation logic in n8n stays the same.
Build a better n8n Google Maps pipeline
Capture free, export clean, automate in n8n, or let the Vonsel dashboard handle the whole thing. Free download. No trial, no credit card. Explore the dashboard or browse the integrations blog.
Can I scrape Google Maps with n8n without the Places API?
Yes. The simplest path is to capture the businesses with the free Vonsel Chrome extension, export the results as CSV or JSON, then feed that file into n8n with a Read Binary File or Webhook trigger. n8n handles enrichment, deduplication, and outreach from there, so you never touch the paid Places API or write a custom scraper.
Is the Vonsel Chrome extension free to use with n8n?
Yes. The Vonsel extension is a free download with no trial and no credit card. You use it to capture Google Maps businesses and export the data. n8n then automates whatever comes next, and the Vonsel dashboard adds a mapped CRM, review intelligence, and AI email per business when you want the workflow handled for you.
What can an n8n Google Maps workflow automate?
Once your Google Maps leads are in n8n you can validate emails, deduplicate the list, push contacts into a CRM, enrich websites, score leads, and trigger cold email or WhatsApp sequences. n8n connects hundreds of apps, so the exported file becomes the fuel for an end-to-end pipeline.
Add Chrome Extension