# Google Maps Lead Scraper > Turn Google Maps into an automated sales machine - Skill: `hayderhekmat/google-maps-lead-scraper` (Agent Skill, multi-file: 7 files) - Install (CLI): `npx skillmds@latest add hayderhekmat/google-maps-lead-scraper` - Raw SKILL.md: https://api.skillmd.com/api/skills/hayderhekmat/google-maps-lead-scraper/raw - Safety review: pending (external: skill-scanner PASS, skillspector CAUTION) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: NOASSERTION - Author: HayderHekmat (https://skillmd.com/u/hayderhekmat) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/hayderhekmat/google-maps-lead-scraper --- # Google Maps Lead Scraper Skill package: `google_maps_lead_scraper` ## What This Skill Does Turn Google Maps into an automated sales machine. Identify high-value prospects with built-in lead scoring and contact extraction. Our unique 'Monitor' technology ensures you never scrape the same business twice, delivering fresh, high-intent leads directly to your workflow every day. This skill is Hermes-ready and designed for Hermes Agent skill workflows. It is also compatible with skill-style agent systems that read markdown instructions, a manifest, and a JSON input schema. ## When To Use It - Google Maps Lead Scraper - Recurring market intelligence: schedule baseline and incremental scans to emit only net-new or changed businesses for ongoing monitoring. - Lead prioritization and routing: generate ranked, scored lead lists and actionable contact enrichment (emails, contact forms, social links) for outreach sequencing. ## Inputs Expected From Normal Users - `location` (string) - Enter a city, region, or country. Example: Berlin, Germany. This stays a standard Google Maps text search unless you also provide geolocation fields or a custom geolocation. - `maxPlaces` (integer) - Stop when this many valid places have been pushed to the dataset. - `maxResults` (integer) - Optional secondary cap. If both maxPlaces and maxResults are set, the lower limit wins. - `mode` (string) - Fast mode is list-only and cheapest. Deep mode allows profile opening and enrichment with strict caps. - Advanced, internal, and cost-sensitive fields remain available in `input_schema.json`, but the agent should not ask about them by default. ## Output Expected The workflow returns an array of records from the Actor's default Dataset. Common record fields: - `place_name` (string) - Business or place name when available. - `address` (string) - Detected street address or location text when available. - `website` (string) - Business website URL when available. - `rating` (number) - Google Maps rating when available. ## Step-By-Step Workflow 1. Read the user's goal and map it to one of the detected capabilities. 2. Validate required inputs against `input_schema.json`. 3. Ask for missing required values before making any external call or Actor run. 4. Execute the documented API, repository tool, or Apify Actor workflow described by the source. 5. Return a concise summary, structured result data, and any relevant links or dataset references. 6. For long-running work, report progress and preserve enough context for retry. ## How This Skill Calls The Apify Actor - Actor slug: `solutionssmart/google-maps-lead-scraper` - Required secret: `APIFY_TOKEN` - Start run endpoint: `https://api.apify.com/v2/acts/solutionssmart~google-maps-lead-scraper/runs` - Run-sync endpoint: `https://api.apify.com/v2/acts/solutionssmart~google-maps-lead-scraper/run-sync-get-dataset-items` - Expected result: dataset items from the default dataset - Input schema source: `apify_actor_metadata` - Readiness level: `validated` ## Before Running - Verify `APIFY_TOKEN` exists in the agent secret store. - Validate user input against `input_schema.json`. - Use the run-sync endpoint for small jobs. - Use the async run endpoint for larger jobs and then fetch dataset items. ## Required And Conditional Inputs Always-required fields: - No always-required fields were confirmed. Conditional requirements depend on the selected mode, action, operation, or task: - No high-confidence conditional requirements were inferred. ## Field Guidance For Agents By default, the agent should only ask about agentDefaultFields. Advanced fields should be used only when the user explicitly requests expert control. ### Default Workflow - Default mode: `fast` - Ask first: `location`, `maxPlaces`, `maxResults`, `mode` ### Ask The User First `location`, `maxPlaces`, `maxResults`, `mode` ### Conditional-Only Fields none These fields are valid and user-facing, but they should not be requested by default. Ask for them only when the user selects a mode, action, or operation that requires them. Apply `conditionalRequirements` before asking for these fields. ### Ask Only If Needed `geolocation`, `customGeolocation`, `useProxy`, `maxConcurrency`, `detailsConcurrency`, `enableDetailsConcurrencyOverride`, `contactEnrichmentConcurrency`, `navigationTimeout` These are technical or expert options. Use them only when the user asks for advanced behavior or operational tuning. ### Do Not Ask Normal Users none These are billing, debug, storage, telemetry, or internal fields. Normal users should not be asked about them. ### Cost-Sensitive Fields `maxPlaces`, `maxProfiles`, `maxEnrichments`, `maxResults`, `maxRunTimeSec`, `maxCrawledPlacesPerSearch`, `enableEnrichment`, `includePlaceDetails`, `includeEnrichment`, `includeReviews`, `useProxy`, `maxConcurrency`, `detailsConcurrency`, `enableDetailsConcurrencyOverride`, `contactEnrichmentConcurrency`, `rateLimit`, `maxDetailsToFetch`, `n8nPromptMaxBytes` These can increase runtime, compute, memory use, scraping depth, or external requests. Warn the user before enabling or increasing them. ## Cost-Safe Execution - Risk level: `high` - Recommended test input: ```json { "maxPlaces": 5, "maxResults": 5, "includeReviews": 0 } ``` - Safe defaults: ```json { "maxPlaces": 5, "maxResults": 5, "includeReviews": 0 } ``` - High-cost fields: `maxPlaces`, `maxProfiles`, `maxEnrichments`, `maxResults`, `maxRunTimeSec`, `maxCrawledPlacesPerSearch`, `enableEnrichment`, `includePlaceDetails`, `includeEnrichment`, `includeReviews`, `useProxy`, `maxConcurrency`, `detailsConcurrency`, `enableDetailsConcurrencyOverride`, `contactEnrichmentConcurrency`, `rateLimit`, `maxDetailsToFetch`, `n8nPromptMaxBytes` Agent guidance: - Start with a small maxPlaces, maxItems, or maxResults value for test runs. - Disable review scraping unless explicitly requested. - Disable website enrichment for first validation runs. - Use async runs for large jobs. ## Error Handling - If an input is missing or ambiguous, ask a targeted follow-up question. - If the source API or Actor returns a validation error, explain the failing field and suggest a corrected input. - If rate limits or transient network errors occur, retry once with backoff and then report the failure clearly. - If the source documentation is incomplete, state the assumption and keep raw response details visible. ## Safety And Rate-Limit Notes - Respect the terms, robots policies, and rate limits of the source service. - Do not expose API keys, Apify tokens, or personal data in logs or final answers. - Prefer small test runs before large scraping or API jobs. - Avoid browser rendering unless the workflow explicitly requires it. ## Example User Commands - "Use `google_maps_lead_scraper` to run the default workflow for this source." - "Generate a request for `google_maps_lead_scraper` using these parameters: ..." - "Validate this `google_maps_lead_scraper` input before running it." - "Retry the failed `google_maps_lead_scraper` operation and explain what changed." ## Integration Notes For Hermes Agent Copy this folder into `~/.hermes/skills//google_maps_lead_scraper/` or install it with `hermes skills install `. Keep `SKILL.md`, `manifest.json`, and `input_schema.json` together so the agent can load the instructions and validate user input.