GeoScraper Google Map Scraper icon

GeoScraper Google Map Scraper

Unified node for GeoScraper Google Map Scraper operations

Overview

This node, named "GeoScraper Google Map Scraper," provides unified access to various Google Maps scraping operations via the GeoScraper API. It allows users to programmatically retrieve data such as map search results, place search results, detailed information about a single place, and reviews for a place.

The Review operation specifically scrapes Google Maps reviews for a given place identified by its unique place data ID. This is useful for businesses or analysts who want to gather customer feedback and sentiment analysis from Google Maps without manual browsing.

Practical examples:

  • Collecting all user reviews for a restaurant or hotel to analyze customer satisfaction.
  • Aggregating reviews over time to monitor reputation changes.
  • Using review data in dashboards or reports for business intelligence.

Properties

Name Meaning
Place Data ID The unique identifier (data_id) of the place whose reviews you want to scrape.
Next Page Token (Optional) Token to fetch the next page of reviews if pagination is supported.
Language Language code (e.g., "en") to specify the language of the response data.
Use Cached Boolean flag indicating whether to use cached data if available, reducing API calls.

Output

The node outputs an array of JSON objects representing the scraped reviews. Each item corresponds to a single review or a batch of reviews depending on the API response.

  • The json output field contains the review data with details such as reviewer name, rating, comment, date, etc. (exact fields depend on the API response).
  • If there are no more reviews, the node outputs a JSON object with a message "No more results" and detail "No data found".
  • Pagination is supported via the "Next Page Token" input property; subsequent pages can be fetched by providing this token.

The node does not output binary data.

Dependencies

  • Requires an API key credential for the GeoScraper service (referred generically as an API token).
  • Makes HTTP POST requests to the GeoScraper API endpoints.
  • Needs network connectivity to https://api.geoscraper.net.

Troubleshooting

  • Common issues:

    • Missing or invalid place data ID will cause errors.
    • Providing an incorrect or expired API token will result in authentication failures.
    • If the "Next Page Token" is invalid or expired, no further results will be returned.
  • Error messages:

    • "You must provide a value for the selected ID type." — occurs if the required place identifier is missing.
    • "No more results" with detail "No data found" — indicates that there are no additional reviews to fetch.
    • Network or API errors will throw exceptions; enabling "Continue On Fail" allows processing to continue with error info in output.
  • Resolution tips:

    • Ensure the place data ID is correctly copied from a valid source.
    • Verify the API token is set up properly in n8n credentials.
    • Use the "Use Cached" option to reduce unnecessary API calls and avoid rate limits.
    • Handle pagination tokens carefully to iterate through all reviews.

Links and References

Discussion