Google Maps to Google Sheets, leads ready to pitch
Copying businesses from Google Maps into a spreadsheet sounds simple until you do it for an hour and realize you’ve only captured 20 leads, half of them missing phone numbers, and you still need to dedupe.
Agency owners feel this when a client asks for “just 200 local leads by tomorrow.” A sales rep trying to hit daily outreach targets runs into the same wall. And if you manage marketing for a local service business, Google Maps leads automation is the difference between “we’ll do outreach this week” and “we did outreach today.”
This workflow scrapes Google Maps using BrowserAct, drops clean rows into Google Sheets, and pings you in Telegram the moment new leads land. You’ll see how it works, what you need, and what to watch out for before you run it at scale.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Maps to Google Sheets, leads ready to pitch
flowchart LR
subgraph sg0["When clicking ‘Execute workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Run a workflow task", pos: "b", h: 48 }
n2@{ icon: "mdi:cog", form: "rounded", label: "Get details of a workflow task", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code in JavaScript"]
n4@{ icon: "mdi:database", form: "rounded", label: "Append or update row in sheet", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Send a text message"]
n3 --> n4
n1 --> n2
n4 --> n5
n2 --> n3
n0 --> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n4 database
class n3 code
classDef customIcon fill:none,stroke:none
class n3,n5 customIcon
The Problem: Google Maps lead scraping is slow and messy
Manual Google Maps prospecting is sneaky expensive. You start with good intentions, then you’re bouncing between tabs, copying business names, trying to capture websites, guessing categories, and pasting everything into a sheet that quickly turns into chaos. Then come the duplicates, because the same business appears in multiple searches or you grabbed it last week and forgot. Worst part: by the time your list is “ready,” your competitors may have already emailed the best prospects.
The friction compounds, especially when you repeat it every week.
- Each search session turns into an hour of copy-paste, and you still need to clean the sheet afterward.
- Duplicates creep in fast, so outreach gets awkward (“Didn’t you email us yesterday?”).
- It’s hard to stay consistent across teammates, which means lead quality swings day to day.
- You don’t get notified when the list is ready, so scraping finishes and nobody acts on it.
The Solution: Scrape Maps, write to Sheets, get alerted
This n8n workflow turns Google Maps searching into a repeatable lead-capture system. You run it manually when you want a fresh batch of prospects, set your location and business category, and let BrowserAct handle the scraping job. When the scrape finishes, the workflow parses the results into individual businesses and writes them into Google Sheets. It also matches leads on the “Name” column, so you’re updating existing rows instead of creating duplicates. Finally, it sends you a Telegram message with the new lead’s details, so your next action is obvious: open the sheet and start outreach.
The workflow starts with your search criteria (location, category, and how many leads to pull). Then BrowserAct runs and the workflow waits until the task is complete. Once results are parsed, Google Sheets becomes your clean source of truth and Telegram becomes your real-time “new leads are ready” alert.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you need 100 roofers in a specific suburb. Manually, you might spend about 2 minutes per business between opening profiles, copying the name, website, phone number, and pasting into Sheets, which is roughly 3 hours for the list. With this workflow, you spend about 5 minutes setting the location and category, then wait while BrowserAct scrapes and n8n writes everything into Google Sheets. You get a Telegram alert when it’s done, and your “work” becomes outreach, not data entry.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- BrowserAct to scrape Google Maps search results.
- Google Sheets to store and dedupe leads.
- Telegram bot token (get it from BotFather in Telegram).
Skill level: Intermediate. You’ll connect accounts, add an API key, and edit a few fields like location and category.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You trigger it when you need leads. This workflow is started manually, which is useful when you’re building lists on demand for a campaign, a new client, or a new territory.
BrowserAct runs the Google Maps scrape. You set the Location, Bussines_Category, and the number of leads to pull in the first BrowserAct node. Then a second BrowserAct node monitors the job and waits until the task is fully complete.
The raw output is cleaned up into usable rows. A code step parses the JSON string coming back from the scraper and splits it into individual items, one per business, so Sheets can handle it neatly.
Google Sheets becomes your live lead database. Each business is appended or updated, matching on “Name” to cut down duplicates. Once the sheet is updated, Telegram sends you a message with the new lead details.
You can easily modify the search criteria (location, category, and volume) to fit different niches or cities based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
This workflow starts with a manual run, then kicks off a scraping task and follows it through completion.
- Add and open Manual Execution Start to confirm it is the entry point.
- Connect Manual Execution Start to Launch Scrape Task to match the execution flow.
Step 2: Connect BrowserAct and Launch the Scrape
These nodes start the scraping job and wait for it to complete before parsing the results.
- Open Launch Scrape Task and set Workflow ID to
[YOUR_ID]. - In Launch Scrape Task → Input Parameters, keep or update: Location =
Brooklyn, Bussines_Category =Baby Care, Extracted_Data =15. - Credential Required: Connect your browserActApi credentials in Launch Scrape Task.
- Open Monitor Task Status and set Task ID to
={{ $json.id }}. - Set Operation to
getTask, Max Wait Time to600, Wait For Finish totrue, and Polling Interval to30. - Credential Required: Connect your browserActApi credentials in Monitor Task Status.
id, Monitor Task Status will fail because ={{ $json.id }} will be empty.Step 3: Set Up Data Parsing
The parsing step converts the scraper’s JSON string output into individual items for sheet updates and alerts.
- Open Parse Scrape Output and paste the provided JavaScript code exactly as shown in the workflow.
- Ensure the script reads
$input.first().json.output.stringand returns an array of items usingreturn outputItems;. - Confirm the connection from Monitor Task Status to Parse Scrape Output.
$input.first().json.output.string is missing, the code throws an error and stops the workflow.Step 4: Configure Output Actions
These steps update Google Sheets and send a Telegram summary for each parsed lead.
- Open Update Spreadsheet Rows and set Operation to
appendOrUpdate. - Set Document to
Test For BrowserActand Sheet toGoogle Maps Local Lead Finder. - Map columns in Update Spreadsheet Rows to the expressions: Url =
{{ $json.Url }}, Name ={{ $json.Name }}, Phone ={{ $json.Phone }}, Rating ={{ $json.Rating }}, Address ={{ $json.Address }}, Category ={{ $json.Category}}, LastSummary ={{ $json.LastSummary }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Update Spreadsheet Rows.
- Open Dispatch Telegram Alert and set Chat ID to
[YOUR_ID]. - Set Text to the multi-line expression:
={{ $('Parse Scrape Output').item.json.Name }} {{ $('Parse Scrape Output').item.json.Address }} {{ $('Parse Scrape Output').item.json.LastSummary }} {{ $('Parse Scrape Output').item.json.Rating }} {{ $('Parse Scrape Output').item.json.Url }} {{ $('Parse Scrape Output').item.json.Category }}. - Credential Required: Connect your telegramApi credentials in Dispatch Telegram Alert.
Step 5: Test and Activate Your Workflow
Run a full test to confirm the scrape, parsing, sheet update, and alert steps work end-to-end.
- Click Execute Workflow on Manual Execution Start to start a manual test run.
- Verify that Monitor Task Status completes and Parse Scrape Output returns multiple items.
- Check Update Spreadsheet Rows to confirm rows are appended or updated in the target sheet.
- Confirm a Telegram message is sent by Dispatch Telegram Alert with lead details.
- When satisfied, switch the workflow status to Active to use it in production.
Common Gotchas
- BrowserAct credentials can expire or need specific permissions. If things break, check your BrowserAct API key and workflow/template access in the BrowserAct dashboard first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default parsing assumptions can be brittle when Google Maps layouts change. If your “Parse Scrape Output” step starts returning missing fields, inspect the raw JSON output and adjust the code to match the new structure.
Frequently Asked Questions
About 30 minutes if your accounts are ready.
No. You’ll mostly connect BrowserAct, Google Sheets, and Telegram, then edit the location/category fields.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in BrowserAct usage costs based on how many leads you scrape.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but you’ll want to plan it. Most people duplicate the workflow and change the Location and Bussines_Category in the “Launch Scrape Task” setup, then write into separate tabs (or separate Sheets) per city. You can also loop through a small list of cities by feeding items into the BrowserAct launch step, but start simple first. If you change dedupe logic, keep the “Update Spreadsheet Rows” match column consistent so your database stays clean.
Usually it’s an expired or incorrect API key, so regenerate it in BrowserAct and update the credential in n8n. It can also be a missing permission for the “Google Maps Local Lead Finder” template, or a blocked run if you’ve hit BrowserAct limits. If the scrape launches but never completes, check the task status output in the “Monitor Task Status” node and confirm it reaches 100%.
Practically, you can pull a few hundred leads per run comfortably, then repeat runs as needed. On n8n Cloud, your monthly execution limit depends on plan (Starter is meant for lighter volumes, Pro handles more). If you self-host, there’s no execution cap, but your server and BrowserAct usage limits still matter. For stability, most teams start with batches of about 100 to 300 leads per scrape and scale up once the sheet format is dialed in.
For this exact use case, n8n is usually the better fit because the “hard part” isn’t moving data from A to B, it’s handling a scraping job, waiting for completion, parsing JSON, and deduping in Sheets. Zapier and Make can do pieces of that, but the workflow gets expensive and awkward once you add branching, batching, and code-based parsing. n8n also gives you the self-hosting option, which is honestly a big deal when you’re doing lead gen regularly. If you only need a simple “new row in Sheets to Slack” automation, Zapier or Make is fine. Talk to an automation expert if you want help choosing.
Once this is running, lead capture becomes a button you click, not a chore you dread. The workflow handles the repetitive stuff. You handle the pitching.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
