Google Maps Email Extractor & Lead Scraper
Pricing
from $4.50 / 1,000 results
Google Maps email extractor API: business emails, graded deliverability and a 0-100 lead score for $7 per 1,000 leads. Finds contact pages under their native name (impressum, kapcsolat, contatti +44, ten languages); MX, SPF, DMARC, catch-all checks. Local business email finder for B2B leads.
REQUIRED unless you set startUrls: the run needs at least one of the two, and it will stop immediately if both are empty. List of search queries to use on Google Maps (e.g., 'restaurants in Budapest', 'dentists in London'). Each query will produce a separate search.
[ "restaurants in Budapest", "dentists in London"]An alternative to searchQueries: supply one and leave the other empty. Direct Google Maps search result URLs. Use this if you already have specific Google Maps URLs to scrape.
Maximum number of business listings to extract per search query. Set to 0 for unlimited. Default and form prefill: 25, enough to judge output quality on a real market. Runtime is roughly 70 s of startup plus 5-8 s per lead, so no run returns within a 30-45 s tool-call window: if you call this Actor programmatically or from an AI agent, pass maxResults explicitly, poll the run, then read the dataset. For production runs use 100-1000 and raise maxRunSeconds to match (the run stops at that time budget). Billing: $0.007 per delivered lead on the Free plan, $0.006 Bronze, $0.005 Silver, $0.0045 on Gold, Platinum and Diamond (all enrichment included at every tier), plus a $0.015/GB run-start fee ($0.06 on the 4 GB default, the same on every plan). Example on the Free plan: 100 leads = $0.76, 1,000 leads = $7.06. Bigger runs are cheaper per lead because the start fee amortises. Runs of several hundred leads can also need a longer Apify run timeout (Start new run, Options, Timeout). The scraper estimates the runtime at startup and, with autoExtend on, restarts itself with a longer timeout if your settings would not fit.
Visit each business website to extract email addresses. Disabling this speeds up the scraper significantly.
Extract social media profile links (Facebook, Instagram, LinkedIn, Twitter) from business websites.
Language code for Google Maps results (e.g., 'en', 'de', 'hu').
When enabled, the scraper fetches each business's Facebook page to extract the numeric page ID, then builds a targeted Meta Ad Library URL (active ads only). Adds ~1 request per business with a Facebook URL. Great for identifying actively-advertising leads (high purchase intent).
When enabled, the actor grades every primaryEmail before delivery: checks MX records, SPF & DMARC DNS entries, and attempts an SMTP RCPT TO probe to detect catch-all domains (high bounce risk). Fills the emailValidation field with deliverability 'high'/'medium'/'low'. Critical for cold-outreach teams protecting sender reputation.
When enabled, the actor extracts lightweight web quality signals from every homepage it already fetches: HTTPS-only, mobile-responsive, page size, favicon, Open Graph tags, structured data. Fills webSignals + webQuality ('modern'/'dated'/'poor'). Free (uses HTML already in memory). Perfect for web-agency outreach targeting.
Return only places that earlier runs of this watch list did not deliver: they are skipped before anything is scraped and not charged (the run-start fee still applies to every run). The first run returns everything, all marked as new. Combine with a Schedule for a daily alert. "Maximum Results Per Query" counts the places checked, new or not, so set it above the number you expect.
Optional. Names the list of leads already delivered. Empty: the search itself is the list (change the search and the list starts over). The same name keeps the list when you edit the search; different names keep several lists apart.
How long the run may work before it stops by itself, in seconds. When the budget is used up the run stops starting new places and pages, finishes the ones in progress, saves everything collected and ends as SUCCEEDED with the message "Stopped at the time budget: N leads saved. Raise maxRunSeconds for more." Leave empty or 0 for no time budget (default). Roughly 70 s of startup plus 5-8 s per lead: set 900 for about 100 leads, 3600 or more for 500+. Values 1-29 count as 30. The Apify run timeout still applies on top of this.
Maximum number of pages processed in parallel. Lower values reduce the chance of being blocked.
Proxy configuration for the scraper. The default (Apify datacenter proxy) was measured on four markets in paired runs against RESIDENTIAL: same rows delivered, same email hit rate, ~78% cheaper. Switch to the RESIDENTIAL group only if your runs hit Google's consent wall or return nothing — that is Google throttling datacenter IPs, and RESIDENTIAL gets past it at $8/GB.
Maximum concurrent requests when scraping business websites for emails. Keep low to avoid blocks.
Optional, and it requires state: you have to remember the datasetId that a previous run returned and pass it back here. Leave it empty on a first run. If you provide a dataset ID from a previous run, the actor will skip any Google Maps place already present there (matched by placeId). Perfect for daily/weekly scheduled runs that only want NEW leads — you save on every duplicate. Example: '0selLasyFyBlq5xRq' from a previous run.
⭐ Recommended. If your run's timeout is too short for the requested maxResults, the actor automatically starts a fresh run with a sufficient timeout instead of refusing. You never have to adjust the timeout manually. Note for programmatic callers: when this fires, the run you started finishes early and your results live in a SECOND run with a different runId, named in the first run's status message. Follow that pointer rather than reading the first run's empty dataset. Billing is unchanged — PAY_PER_EVENT only charges for leads actually delivered, regardless of which run delivered them. The original run exits cleanly with a pointer to the new run's dataset. Set to false only if you want the preflight to refuse with a detailed error instead.
🎯 Power feature. Google Maps caps a single search result list at ~120 places. If you need comprehensive coverage of a large city (say all 800+ restaurants in Manhattan), set this to N and the actor splits the search area into an N×N geographic grid, issuing the same query against each tile's map viewport. Tile results are de-duplicated by placeId so you get a single clean dataset. Leave at 1 (default) for small cities or when the 120-cap isn't a concern. Try 3 (→9 tiles) for medium cities, 5 (→25 tiles) for big cities, up to 10 (→100 tiles) for NYC/Tokyo-scale coverage. Only works when your query contains a recognizable location (e.g. 'restaurants in Manhattan', 'dentists near Berlin') — geocoded free via OpenStreetMap/Nominatim. ⚠️ Billing impact: each extra lead still costs one lead at your plan rate ($0.007 Free down to $0.0045 on Gold, Platinum and Diamond), and the run-start fee is charged once regardless of tile count — so 5× tiles doesn't mean 5× cost, it means up to 5× unique leads discovered.
Alias for "Search queries", accepted so an input written for compass/crawler-google-places runs here unchanged. If both are set, "searchQueries" wins.
Alias for "Max results". If both are set, the alias wins: the platform writes schema defaults into every input, so the native field is always present and the explicitly supplied alias is the stronger signal of intent.