
Google Maps Email Finder
Google Maps Email Finder is a reusable BrowserAct template for collecting structured records from public Google Maps pages.
Brief
Google Maps Email Finder is a reusable BrowserAct template for collecting structured records from public Google Maps pages. Configure the run inputs, start the Bot, and receive consistent output for research, monitoring, enrichment, or downstream automation without writing selectors or scraper code.
What Does BrowserAct Google Maps Email Finder Do?
The Bot starts from your configured inputs, opens the relevant public Google Maps page, loads the requested records, extracts the visible fields, and returns structured results. The default example uses marketing agency for Keyword, but the input can be changed before each run.
Key Features of Google Maps Email Finder
- Configurable public-page inputs without rebuilding the Bot.
- Structured records returned in a consistent
resultsarray. - Public, non-login extraction path.
- Reusable runs for new keywords, URLs, locations, or limits.
- Output ready for review, export, API use, or automation.
What Data Can I Extract from Google Maps?
Field | Description |
|---|---|
| Publicly visible business name value for the record, when available. |
| Publicly visible category value for the record, when available. |
| Publicly displayed address. |
| Publicly displayed phone number. |
| Public website URL associated with the record. |
| Public email addresses visible on the business website. |
| Publicly visible contact page url value for the record, when available. |
| Publicly visible google maps url value for the record, when available. |
| Record position in the collected result order. |
How to Use Google Maps Email Finder
Quick Start Guide
- Click Run task.
- Keep the default inputs for a first test or enter your own public-page values.
- Click
Run. - Review the structured records after the run completes.
- Download the result or connect it to another workflow.
Input Parameters
Parameter | Required | Default | Description |
|---|---|---|---|
| Yes |
| Controls the keyword used for this run. |
| Yes |
| Controls the country used for this run. |
| Yes |
| Controls the max business count used for this run. |
Example Output
{
"results": [
{
"business_name": "Example value",
"category": "Example value",
"address": "Example value",
"phone": "Example value",
"website_url": "https://example.com/public-record",
"email_addresses": [],
"contact_page_url": "https://example.com/public-record",
"google_maps_url": "https://example.com/public-record",
"rank": 1
}
]
}
How Does it Work?
- Search public Google Maps using the configured keyword and country bias.
- Collect listing URLs from the result feed and open each public business detail page.
- Follow the official website and a clearly linked contact page, then collect visible public emails and business fields.
- Return structured business records, using an empty email list when no public address is visible.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the data you need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Describe the public website, records, inputs, fields, and result limit.

Step 2: Let BrowserAct build and test the Bot
BrowserAct explores the live website, determines the navigation and extraction path, and validates the result. Reply in the same build conversation if the Agent requests a missing public URL, field, or expected output.

Step 3: Run the Bot and review the result
Run the completed Bot with default inputs. Check record count, source URLs, and required fields before reusing it with new inputs.


Why Use Google Maps Email Finder?
- Replace repetitive copying from public Google Maps pages.
- Keep the same output structure across repeated runs.
- Send public records into research, reporting, enrichment, or monitoring workflows.
Who Can Use Google Maps Email Finder?
- Researchers and analysts collecting public web data.
- Marketing, sales, and operations teams preparing structured datasets.
- Automation builders connecting BrowserAct output to other tools.
- Developers who need reusable browser-collected JSON records.
Automation and Export

BrowserAct returns structured records first. You can then use that output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual spreadsheet export.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com
