Make.com + Google Maps Automate your local leads without touching an API

Capture businesses free in your browser, export a clean CSV or JSON, then let Make.com do the routing, enrichment, and delivery. Here is the full workflow.

Integrations · Jul 2026 · 7 min read

Key takeaways

Capture Google Maps businesses with the free Vonsel Chrome extension, then export CSV or JSON. No API key, no billing.
Make.com reads that file (Google Sheets, Drive, or Parse CSV) and pushes each row wherever you want: CRM, sheet, email tool, or webhook.
The extension is the means. The Vonsel dashboard (mapped CRM, review and email intelligence, AI email per business) is the end.

The idea in one line

Capture in the browser, automate in Make

Most guides to Google Maps automation start with the Google Places API: create a project, add a billing card, watch the per-call cost tick up, and wire the responses into your scenario. It works, but it is slow to set up and easy to overspend on.

There is a simpler path. You capture the businesses you actually care about with a free Chrome extension, export them as a structured file, and hand that file to a Make.com scenario. The extension is the means. What you do with the data is the end.

This keeps the capture step visual and human (you see the map, you pick the area) while Make handles the repetitive plumbing: deduplication, enrichment, routing to the right destination, and notifications. No code, no API console.

Start with the capture step

Grab the extension, scrape a search, and export in one sitting. Free download. No trial, no credit card.

Add Chrome Extension

API keys or billing accounts needed to capture the data

file formats to export: CSV, XLSX, and JSON

Make scenario to move every lead to its destination

Step 1

Capture the businesses on Google Maps

Open Google Maps, search a category and location (for example "roofers in Austin"), and let the Vonsel extension collect the visible results: name, address, phone, website, rating, review count, and category. If you want emails and social profiles, the extension can enrich each listed website invisibly as it captures.

When the capture finishes, export the list. For an automation pipeline, JSON is the cleanest handoff because the structure is unambiguous, but CSV works everywhere and is the easiest to import. If you are unsure which to pick, our guide on CSV, XLSX, and JSON export options breaks down when each one fits, and exporting Google Maps data to CSV covers the format most Make modules expect.

The reason the no-API path matters: Google meters and rate-limits the Places API, and pricing scales with volume. A browser capture sidesteps quota math entirely, so you can pull the exact slice of a city you plan to work, not whatever your budget allows that month.

Step 2

Get the file into Make.com

Make cannot read a file sitting on your desktop, so give it somewhere to look. There are three reliable options, and all of them avoid custom code.

Method	How it works	Best for
Google Sheets	Paste or upload the CSV into a sheet, use the Watch Rows trigger	Recurring lists you update often
Google Drive	Drop the file in a folder, use Watch Files then Parse CSV	One-off batches by area
Parse CSV	Upload directly to the scenario or via webhook	Ad-hoc runs and testing

The Make Google Sheets module is the most popular route because a sheet doubles as a staging area you can eyeball before anything downstream runs. Point Watch Rows at your sheet, and every new business becomes a bundle Make can act on.

Step 3

Build the scenario logic

Filter before you route

Add a filter so only businesses that match your criteria continue: rating below 4.0, no website, or a specific category. This keeps low-value rows out of your CRM.

Deduplicate

Use a data store or a search step to skip businesses you already contacted. A place name plus address makes a solid unique key.

Enrich

Call an email verification or company lookup module to add missing fields before the record lands anywhere permanent.

Route with a router

Send businesses without a website to one branch (web design pitch) and everyone else to another. One scenario, multiple outcomes.

Deliver

Create the record in HubSpot, Pipedrive, Airtable, or Notion, then post a Slack alert so a rep picks it up the same day.

Schedule

Set the scenario to run on a timer so any file you drop in the watched folder gets processed automatically overnight.

If your destination is a CRM, our walkthrough on moving Google Maps leads into your CRM covers the field mapping in detail, and sending Maps leads to HubSpot shows the exact module setup for that platform.

You still need clean input first

Make can only route what you capture. Start the pipeline with a solid export. Free download. No trial, no credit card.

Add Chrome Extension

Make vs the other options

When Make is the right tool

Make.com sits between the simplicity of Zapier and the flexibility of n8n. Its visual scenario builder is more forgiving than raw code, and its per-operation pricing tends to be friendlier for high-volume lead processing than trigger-based tools.

If you are weighing platforms, compare this guide with the same workflow in Zapier or the self-hosted route in scraping Google Maps with n8n. The capture step is identical in all three: a free browser export is what feeds them.

Whatever you choose, keep the same discipline you would with any sourced list. Emailing local businesses has rules, and the safest approach is to send relevant, wanted outreach. Our note on whether scraping Google Maps is legal is worth a read before you automate outreach at scale.

A scenario is only as good as its input. Capture well, and the automation runs itself

The native alternative

Or skip the plumbing entirely

Building a Make scenario is worth it when you need data in a system you already run. But there is a shortcut for the most common goal, which is turning a captured list into leads you can actually work.

The Vonsel dashboard is the destination the extension feeds by default. Every capture lands in a mapped CRM: businesses plotted on a map, organized by area, with review and email intelligence attached. It writes an AI email tailored to each business from that business's own context, and it builds contextualized, value-added databases instead of a raw spreadsheet you still have to clean.

In other words, the same file you would hand to Make already has a home that understands what a local lead is. You can do both: automate the edge cases in Make, and keep your core prospecting in the mapped CRM. Compare the raw-file approach with an enriched one in Google Maps data vs bought lists.

Capture once, automate anywhere

Export to Make, or let the Vonsel dashboard turn the list into a mapped CRM with AI email per business. Free download. No trial, no credit card. See plans or explore features.

Add Chrome Extension

Frequently asked questions

Do I need the Google Places API to send Maps leads to Make.com?

No. You can capture businesses directly in your browser with the free Vonsel Chrome extension, export a CSV or JSON file, and feed it into a Make.com scenario. That avoids Places API keys, billing, and usage quotas entirely.

How do I import a CSV of Google Maps leads into Make.com?

Upload the exported CSV to Google Drive or Sheets, then use the matching Make module (Watch Rows or Parse CSV) as the trigger. Map each column to fields in your destination app and add the routers, filters, or enrichment steps you need.

Is the Vonsel Chrome extension really free?

Yes. The extension is a free download with no trial and no credit card. It captures business data on Google Maps and exports it. The Vonsel dashboard adds a mapped CRM, review and email intelligence, and AI email per business on top.