密码Google Maps Business Leads Scraper
DeprecatedPricing
Pay per usage
Search Google Maps Extract business leads by category, keyword, and location across 18 languages. Returns phone, website, rating, hours, popular times, services, and more.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
wang wei
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
a month ago
Last modified
Categories
Share
All notable changes to this Actor are documented in this file.
The format is based on Keep a Changelog , and this project adheres to Semantic Versioning .
maps.example.internal / api.maps-listing-source.com). Replaced with the real upstream https://api.dataforseo.com so requests actually reach the data provider. (Internal code only — README, schema, store listing, and other user-visible surfaces remain free of any upstream-vendor references.)language_code from outgoing request bodies. The business_data/business_listings/search/live endpoint derives language from the resolved location; sending language_code was a leftover from an earlier draft and risked a 400 on strict parsers.ENOTFOUND) so future outages are easier to diagnose from run logs.End-to-end smoke test against the real upstream with the credentials baked into actor.json:
categories: ["pizza_restaurant"] + location_coordinate: 53.476225,-2.243572,10 → 200 items, sample Stockport Pizza House / place_id ChIJnXeOjX6ze0gRPQLyO7UuJ4s.categories: ["lawyer"] + location_name: "Los Angeles,CA,United States" → 200 items, sample Gonzalez Richard / 1425 W Lugonia Ave, Redlands, CA 92374.actor.json. The runtime was reading MAPS_API_LOGIN / MAPS_API_PASSWORD from process.env, but the credentials are baked into .actor/actor.json as API_EMAIL / API_PASSWORD. Renamed all code references to match: code now reads process.env.API_EMAIL and process.env.API_PASSWORD. Tests updated accordingly.MapsApiClient constructor now reads API_EMAIL / API_PASSWORD instead of the old variable names.Actor.openKeyValueStore() with no name argument). Previously the code opened a named external store free-tier-limits which required explicit permission grants and failed at runtime with Insufficient permissions for the key-value store. Switching to the default store (auto-permissioned, persists across runs of this Actor) removes the permission requirement entirely.KV permission denied, KV not found, and generic KV unavailable, so support and ops can diagnose quickly.Free tier limit reached substring (previously fell through to the KV-unavailable message because the limit-reached branch didn't set an error code).queries[] array wrapper from the input schema. The Actor now accepts a flat input shape:
categories (string, textarea, required) — one category per line, max 10.locations (string, textarea, required) — one location per line.keywords (string, textarea, optional) — one keyword per line, max 20.language (string, text field, optional) — defaults to English.keywords joined into the task title / description. Want multiple search jobs? Submit multiple Actor runs — each run is one search job.queries[] array of objects could not be rendered correctly by the Apify Console form (schemaBased editor does not support title / editor / nested properties.title inside items). Flattening makes the form render reliably across Console and API clients.src/main.js:
validateInput() rewritten to validate flat fields.expandTasks() now returns { tasks, cats, locs } so the run summary can report input dimensions.categories and locations counts instead of a queries count.queries[] of objects — users saw should be string errors on every entry even when the payload was valid. Flattening the schema eliminates the class of form-validation bugs while keeping the underlying task expansion identical.
queries[].categories, keywords, locations changed from
stringList (one input box per item) to string with textarea editor.
Users now paste one value per line into a single text box.main.js adds splitLines() to parse newline-separated values.validateInput updated to check non-empty lines and category cap.stringList rendered each item as
a separate input field, causing users to fill each row with one character
instead of a complete value. textarea shows a single multi-line box that
matches the mental model "one value per line".queries[].locations simplified from array of {name|coordinate}
objects to a flat array of strings. Each string is auto-detected as either a
city name ("Los Angeles,CA,United States") or GPS coordinates
("34.0522,-118.2437,25").queries[].filters and queries[].order_by input fields.
The Actor no longer exposes advanced filtering / sorting controls. Use multiple
queries with different categories / keywords / locations to broaden results.locations[i] is a non-empty string."queries.0.locations" should be array when users submitted coordinate strings
in the Bulk edit view of an object-typed array.@secretName references to inline values
directly in actor.json (API_EMAIL, API_PASSWORD, RESEND_API_KEY)..actor/output_schema.json) following the official
Actor output schema
specification. Exposes two output references:
results → default dataset items (one business per row).summary → default Key-Value Store SUMMARY record.actor.json specification.
categories, shortDescription, defaultRunOptions).defaultMemoryMbytes / minMemoryMbytes / maxMemoryMbytes.readme and buildTag fields.main.js entry point. Actor.main() now wraps the entire flow
and SDK initialization/exit is handled internally per Apify SDK conventions.await Actor.exit(msg) calls with throw new Error(msg)
so failed runs properly enter the FAILED terminal state on the platform.COPY package.json package-lock.json + npm ci for better build cache hits.place_id → cid → text fallback.query-task, business-result).offset_token (up to 200 results per task, 50 pages cap).