# Google Maps Email Extractor (`george.the.developer/google-maps-email-extractor`) Actor

Turn Google Maps businesses into leads with a verified contact email. Search by keyword with your own Google Places key, or paste website lists to enrich. MX verified, no proxy.

- **URL**: https://apify.com/george.the.developer/google-maps-email-extractor.md
- **Developed by:** [George Kioko](https://apify.com/george.the.developer) (community)
- **Categories:** Lead generation, Business
- **Stats:** 1 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event + usage

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Google Maps Email Extractor

Turn Google Maps businesses into a lead list with a verified contact email. Two ways to run it, both with no proxy.

- **Search mode**: give a query like "dentists in Austin TX" plus your own Google Places API key. You get the businesses, and each one enriched with a contact email.
- **Enrich mode**: already have a list of business websites from any Google Maps scraper? Paste them and get a verified email per site. No API key needed.

The email is the part that matters, and it is the part most scrapers skip. This one scans the homepage, then the contact and about pages if needed, and verifies the email against live MX records so you are not exporting dead addresses.

### How it works

```mermaid
flowchart LR
    A[Query + your Google key] --> B[Google Places: businesses + website]
    A2[Or: paste website list] --> C
    B --> C[For each site]
    C --> D[Scan homepage, then contact and about pages]
    D --> E[Pick best email, prefer on-domain]
    E --> F[MX verify the email domain]
    F --> G[One lead: business, phone, website, email, verified]
```

### Each lead row

- **business**, **address**, **phone**
- **website** and **domain**
- **email**, **emails** (all found), **email\_verified** (MX checked)
- **rating**, **rating\_count**
- **source**, **fetched\_at**

### Why your own Google key

A raw Maps scrape needs paid proxies and fights Google's anti bot. Using the official Places API with your own key is reliable, cheap, and Google gives a monthly free credit that covers most lead runs. You pay Google directly for the search, nothing hidden. Enrich mode needs no key at all.

### Standby / API mode

```
GET /enrich?website=example-dentist.com
GET /search?query=dentists in Austin&key=YOUR_GOOGLE_KEY&limit=20
```

### Pricing

Pay per event: $0.25 per batch run, $0.04 per business lead, $0.10 per lead with an MX verified email. Leads without an email only pay the per lead rate.

### Notes

Email hit rate is highest for small and mid size local businesses, which are the useful outreach targets. Big national chains rarely publish a plain email. The scan stays on each business's own site, so no proxy is used and the run is cheap.

# Actor input Schema

## `query` (type: `string`):

What to find on Google Maps, e.g. 'dentists in Austin TX'. Needs your own Google Places API key below. Leave empty if you are enriching a website list instead.

## `googleApiKey` (type: `string`):

Your own Google Places API key. You pay Google directly (they give a free monthly credit). Only needed for search mode.

## `websites` (type: `array`):

Enrich mode: paste business websites or domains (e.g. from any Google Maps scraper) and get a verified email per site. No API key needed.

## `limit` (type: `integer`):

Max businesses per search query. Google Places returns up to 20 per query, so use several specific queries to cover more.

## `maxLeads` (type: `integer`):

Cap on leads returned in one run.

## Actor input object example

```json
{
  "websites": [],
  "limit": 20,
  "maxLeads": 200
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "websites": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("george.the.developer/google-maps-email-extractor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "websites": [] }

# Run the Actor and wait for it to finish
run = client.actor("george.the.developer/google-maps-email-extractor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "websites": []
}' |
apify call george.the.developer/google-maps-email-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=george.the.developer/google-maps-email-extractor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/hKMzDTpJJHUpatdpB/builds/8eHvd1cQZm0b9Qi8S/openapi.json