← Catalogue home · Local Business family
Finding local businesses, watching for newly-opened ones, catching a listing’s unanswered public questions, and tracking home-listing price changes — then turning any of that into a qualified contact — usually means stitching together several manual checks. This guide covers the whole Local/Maps family as one connected workflow, not four separate tools.
| Actor | Job | Public Task |
|---|---|---|
| Google Maps Business Scraper | Discover the current full set of businesses for a category+area | single search · multi-location |
| Google Maps New Business Scraper | Report only businesses newly detected since your last check | quickstart |
| Google Business Profile Q&A Scraper | Catch new unanswered public questions on a listing | quickstart |
| Zillow Listings Scraper | Home listings, price/status delta | quickstart |
Start with Google Maps Business Scraper for the full current picture of a category+area. Two Task shapes exist depending on scope: a single search, or multiple locations in one run for teams tracking a franchise or several competitors at once.
Google Maps New Business Scraper answers a different question: not “what exists,” but “what’s new since I last checked.” With monitorEnabled: true, the first run silently establishes a baseline (no false “new” claims), and every run after that reports only genuinely new listings — the Actor already does this delta computation, so no external diffing logic is needed downstream.
Google Business Profile Q&A Scraper watches a specific listing’s public Q&A tab — a channel where a slow response visibly costs a business a lead.
Zillow Listings Scraper covers home listings rather than businesses, with the same price/status-delta pattern as the business Actors above.
All four Actors are built to run on a schedule and hand off their output, not just produce a one-time dump:
docs/workflows/n8n/. Import any .json file directly into n8n (Workflows → Import from File).docs/workflows/make/README.md.docs/workflows/postman/.The strongest automation in this family chains three Actors end to end:
Google Maps New Business Scraper (new listings, delta already computed)
↓ (only businesses with a public website)
Business Email Finder & Verifier (verified contact email)
↓
Google Sheets (ready-to-work lead list, updated daily)
This is docs/workflows/n8n/flagship-local-lead-pipeline.json — 4 nodes total. Each Actor already does its own hard part (delta detection, email verification), so the workflow itself is orchestration, not custom logic. See the Leads & Verification family for the qualification Actor on its own.
curl "https://api.apify.com/v2/actor-tasks/om_kh~vigia-maps-new-business-monitor-quickstart/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-X POST \
-H "Content-Type: application/json" \
-d '{"searches": ["coffee shops in Austin, TX"], "maxPlacesPerSearch": 10, "monitorEnabled": true, "maxTotalChargeUsd": 1}'
Natural-language requests this family’s Actors already support: “find Google Maps businesses in Austin,” “show new local businesses detected since my last check.” No discovery ambiguity was found for any of these four Actors during review — the existing MCP tool descriptions already match these requests correctly.