Google Maps Email Extractor & Lead Finder

Find Google Maps business listings by keyword and location, with available phone numbers, websites, ratings and review counts. Google Maps Lead Finder can also visit business websites for published emails and social links. Contact coverage varies and results are not an exhaustive business directory.

Quick start

1. Enter a business keyword in Search queries and an optional city in Locations.
2. Start with a small maxLeads value. Enable Include website enrichment if you want published website contacts.
3. Run the Actor, then export the dataset as JSON, CSV or Excel.

{
  "searchQueries": ["plumber"],
  "locations": ["Chicago, IL"],
  "maxLeads": 5,
  "includeWebsiteEnrichment": true
}

searchQueries is required. Without separate locations, put the location in the query itself. maxLeads is a run-wide ceiling, not a guaranteed number of matches. Missing contacts remain empty or null.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Enrich Boston Marketing Agency Leads
• Find Highly Rated Austin Dentists
• Find Chicago Plumbing Leads

What you get

One saved business-lead row with available identity, Maps source link, address, phone, website, rating and review-count fields. Optional website visits can add published email or social links, while optional verification reports attempts and available results rather than guaranteed delivery. Missing contacts remain null or empty.

Who is it for?

• Sales-research teams preparing source-linked local-business review lists.
• Agencies reviewing available public websites and contact channels.
• Market researchers comparing bounded business-category and location samples.
• CRM operations teams checking public listing data before importing records.

How you can use the data

• Prepare a Chicago plumber review sheet. Use the existing query and city recipe with a small saved-lead cap. Keep name, googleMapsUrl, address, phone and website together, then review source listings before adding records to a CRM.
• Review an Austin dentist sample with websites. Use the existing public example or matching query/location settings. Inspect ratings and website links rather than treating the result set as exhaustive coverage or a precise-radius search.
• Inspect published agency contacts. Use the existing Boston marketing-agency sample with website enrichment explicitly enabled. It checks a homepage and up to three relevant internal pages if no email is found there. Keep discovered emails and social links as public-page observations, without scraping social profiles or submitting forms.
• Prioritize in your own system. Export leadScore and its breakdown with source identity and collection time, then sort or review downstream. The score summarizes profile signals rather than predicting sales success, and results are not saved in score order.

Input settings

Defaults below apply when an API input omits the field. The form can prefill a smaller example: maxLeads: 2, website enrichment off and a 12-second enrichment timeout. Check your submitted input.

Setting / API key	Default	Purpose
Search queries / searchQueries	Required	Business keywords. One or more nonempty strings.
Locations / locations	[]	Combine every query with each supplied location.
Maximum leads / maxLeads	100	Maximum saved unique leads across the run.
Language / language	en	Results language hint. 14 supported choices.
Country / countryCode	US	Country targeting hint. 19 supported choices.
Minimum rating / minRating	Unset	Exclude missing ratings and ratings below the threshold.
Require website / requireWebsite	false	Save only listings with a website URL.
Require email / requireEmail	false	Save only leads with a discovered email.
Website enrichment / includeWebsiteEnrichment	true	Look for published emails and social links on business websites.
Website timeout / enrichmentTimeoutSecs	15	Per-page request timeout, from 5 to 45 seconds.
Verify emails / verifyEmails	false	Add optional verification results. Verification attempts are charged.
Verification level / verificationLevel	mx	Choose format, mx or smtp.
Duplicate matching / dedupeStrategy	placeIdAndAddress	Match by identifier and address, or use placeId.
Proxy configuration / proxyConfiguration	Managed configuration	Configure Maps access. See field help for supported settings.
Debug mode / debugMode	false	Additional troubleshooting messages in the run log.

For requireEmail, enable website enrichment explicitly if you want website contact discovery. Explicitly disabling enrichment is respected even when email is required. Language and country are hints, not guarantees of exclusive geographic coverage. No radius or distance filter is provided.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

Each saved row represents a business lead. This is an illustrative shape-only subset, not a claim of an observed business or guaranteed field coverage:

{
  "name": "Example business",
  "address": null,
  "phone": null,
  "website": null,
  "email": null,
  "rating": null,
  "reviewsCount": null,
  "leadScore": 40,
  "enrichment": {
    "homepageFetched": false,
    "emails": [],
    "socialLinks": {},
    "contactPageHint": null
  }
}

Fields	Meaning
name, category, categories	Business name and available classifications.
address, city, postalCode, countryCode, location	Available address components and coordinates. Coverage varies.
phone, website, email	Available phone, website and first discovered usable email.
rating, reviewsCount	Listing rating and number of reviews, when available.
placeId, fid, cid, googleMapsUrl	Available business identifiers and Maps URL.
isOpen, openingHours, plusCode, businessStatus, priceLevel, mainPhotoUrl	Optional place details. These may be null.
leadScore, leadScoreBreakdown	Profile-signal score and component values.
enrichment	Website fetch outcome, emails, social links and contact-page hint.
emailVerification	Present for requested verification of a discovered email. May be null if verification fails.
searchQuery, searchLocation, dedupeKey, scrapedAt	Search context, duplicate-matching key and collection timestamp.

Website enrichment checks the homepage and, if no email is found there, up to three relevant internal pages. It does not submit contact forms or guarantee an email. Social links are links found on those pages, not scraped social profiles.

Email verification can report format validity, MX records, verification status, confidence, provider and disposable/free-provider/role-account flags. format checks syntax, mx adds mail-server checks, and smtp attempts a mailbox check. Mail-server blocks and catch-all domains can make results inconclusive. Verification does not guarantee delivery.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once when a run starts, including runs with no leads. The lead event is charged for each business lead saved. The email-verified event is charged for each requested verification attempt rather than only positive results.

Applicable Apify platform usage is separate. Keep the lead cap small, and enable enrichment or verification only when needed because they can add processing work. See the live Pricing tab for current rates and plan discounts.

Tips for best results

• Start with one specific business term and city. Broad searches can include adjacent categories.
• Inspect strict filters when results are low. Minimum rating excludes missing values, and website or email requirements can remove otherwise useful listings.
• Choose website enrichment explicitly. Email requirements do not override an explicit choice to disable enrichment.
• Keep verification scope with its result. Syntax, MX and attempted SMTP checks are different, and blocked or catch-all behavior can be inconclusive.
• Review source context before sorting scores. Score-based prioritization is your downstream step rather than the Actor's saved order.

Limits and caveats

Listings and contacts depend on source availability, search relevance, access restrictions and selected filters. Language and country are hints rather than guarantees of exclusive geographic coverage. No radius or distance filter is provided, and complete directory coverage is not promised.

A completed search with no usable matches can return an empty dataset. Individual tasks can fail while other searches retain useful rows. If every search task fails with no leads, the run fails. Time limits can leave partial records, without a fixed-runtime or guaranteed-contact promise.

Website enrichment reads the homepage and, when needed, up to three relevant internal pages for published contacts. It does not submit forms, guarantee an email or extract social profiles. Explicitly disabling enrichment is respected even when an email is required.

Verification can check format, add MX checks or attempt SMTP mailbox checks depending on the requested level. Mail-server blocks and catch-all behavior can make results inconclusive. Verification does not guarantee delivery, and attempts are charged even without positive results.

Lead scores summarize profile signals rather than sales probabilities. Listings retain discovery order rather than score order. Ratings and counts are aggregate listing metrics, not individual review text. This independent tool collects accessible listings and published website contacts rather than private account data.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~google-maps-lead-finder/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "searchQueries": [
    "plumber"
  ],
  "locations": [
    "Chicago, IL"
  ],
  "maxLeads": 5,
  "includeWebsiteEnrichment": true
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/google-maps-lead-finder').call({
  "searchQueries": [
    "plumber"
  ],
  "locations": [
    "Chicago, IL"
  ],
  "maxLeads": 5,
  "includeWebsiteEnrichment": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/google-maps-lead-finder').call(run_input={'searchQueries': ['plumber'], 'locations': ['Chicago, IL'], 'maxLeads': 5, 'includeWebsiteEnrichment': True})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and integrations notes

If the run is still running after the wait period, check its status before retrieving defaultDatasetId. Use the Apify API documentation for run status and dataset export. Connect completed runs to your CRM or spreadsheet with Apify integrations or webhooks.

MCP and AI agents

You can ask your AI assistant to collect data with Google Maps Email Extractor & Lead Finder and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Google Maps Email Extractor & Lead Finder. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/google-maps-lead-finder"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Google Maps Email Extractor & Lead Finder by Fetch Cat, or give it the identifier fetch_cat/google-maps-lead-finder.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Google Maps Lead Finder to collect up to 5 plumbers in Chicago, IL with website enrichment enabled. Show Maps links, available phones, websites and published emails, marking missing contacts.”
• “Collect at most 5 dentists in Austin with websites and a minimum rating of 4. Show listing ratings, review counts and source links without claiming complete local coverage or predicting sales success.”
• “Retrieve up to 3 marketing agencies in Boston with website enrichment on and email verification off. Keep available websites, published emails and score components for my manual CRM review rather than inferring private contacts or delivery guarantees.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I extract emails from Google Maps?

Emails generally come from linked business websites, not a guaranteed Maps email field. Enable website enrichment. Some businesses publish only a contact form.

Can I export Google Maps leads to CSV or use an API?

Yes. Export the dataset in Console, or use the API examples above for structured JSON and downstream processing.

Why are there fewer leads than maxLeads?

It is a ceiling. Search availability, filters, duplicates, inaccessible pages and the run time limit can reduce results. Try one broader query and fewer filters first.

Does the lead score sort or verify prospects?

No. It summarizes rating, review-count, website, email and phone signals. Sort exported rows yourself. The score does not establish business quality or outreach success.

How does duplicate matching work?

placeId uses the available identifier, with a name/address fallback. placeIdAndAddress also includes the normalized address in the key, so the same identifier with different addresses may remain separate. Matching applies within a run, not across earlier datasets.

What if I need individual reviews or different place inputs?

Use the related Maps tools below and check their own input contracts. This Actor accepts keyword searches, not a radius selector or a list of place-detail URLs.

Related Actors

• Website Contact Finder — Collect contacts from business websites you already know.
• Email Enrichment — Check email syntax and public mail-domain signals, and find source-matched business addresses on public company pages.
• Email Finder API — Find source-cited business emails for named people on company websites, without guessing addresses.
• Google Maps Places Scraper — Collect public place names, Maps links and available business-listing details.
• Google Maps Reviews Scraper — Collect individual reviews with a dedicated tool.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥