Google Maps Paginator icon

Google Maps Paginator

Paginate Google Maps search results via configurable HTTP proxy

Paginate Results

AI-generated

Summary

Paginate through Google Maps search result pages using a prefetched base URL and a configurable proxy to collect up to a specified maximum number of places, parsing detailed place information from each page.

Inputs

  • Base URL (required) — Prefetch URL extracted from Google Maps HTML shell, used as the starting point for pagination.
  • Max Results — Maximum number of places to collect per viewport; defaults to 240 and capped at 500.
  • Snapshot ID — An identifier passed through to track the parent job or pagination session.
  • Cell — A passthrough grid cell identifier, defaulting to 'auto'.
  • Latitude (passthrough) — Latitude coordinate passed through for contextual tracking.
  • Longitude (passthrough) — Longitude coordinate passed through for contextual tracking.
  • Proxy Source (required) — Choose between manual proxy input or stored credential for proxy settings.
  • Proxy Host (required) — Proxy server hostname; required if Proxy Source is Manual Input.
  • Proxy Port (required) — Proxy server port; required if Proxy Source is Manual Input.
  • Proxy Username (required) — Username for proxy authentication; required if Proxy Source is Manual Input.
  • Proxy Password (required) — Password for proxy authentication; required if Proxy Source is Manual Input.
  • Proxy Country (required) — Country code for proxy server; required if Proxy Source is Manual Input.
  • Advanced Options — Additional parameters to customize pagination behavior, including delay between pages, request timeout, custom session ID, debug logging, raw record inclusion, and Google cookie string for enhanced data access.

Output shape

a single JSON object containing an array of parsed place objects, each with comprehensive details, along with pagination stats and optional debug logs

The output JSON includes 'places' with detailed place data parsed and normalized from Google Maps, plus 'stats' summarizing pagination (last offset, stop reason, seconds elapsed, session ID, pages fetched). If enabled, 'debug_log' is also included. Pagination stops on reaching max results or encountering data caps/errors. Errors can be bubbled up to fail the node if continueOnFail is disabled.

Links

Discussion