SerpApi Official icon

SerpApi Official

Get live Google Search data and more from SerpApi's official node

Actions72

Overview

This node integrates with SerpApi's Google Maps Reviews API to fetch live reviews data for a specific place on Google Maps. It allows users to retrieve detailed review information such as ratings, comments, and metadata about a location identified by either a Google Maps Data ID or Place ID.

Common scenarios where this node is beneficial include:

  • Monitoring customer feedback and sentiment for a business location.
  • Aggregating reviews for market research or competitive analysis.
  • Displaying up-to-date user reviews on websites or applications.
  • Filtering and sorting reviews based on relevance, rating, or recency.

Practical example: A marketing team wants to automatically collect the latest 10 reviews of their store from Google Maps in English, sorted by highest rating, to analyze customer satisfaction trends.

Properties

Name Meaning
Data ID (data_id) Defines the Google Maps data ID for the place. Must be obtained via the Google Maps API. Either this or Place ID must be set.
Place ID (place_id) Unique reference ID for a place on Google Maps. Must be obtained via the Google Maps API. Either this or Data ID must be set.
Additional Fields Collection of optional parameters to refine the search:
- Language (hl) Language code to use for the search results. Supports many languages including English, Spanish, French, Chinese, Arabic, and more. Default is English (en).
- Sort By (sort_by) Criteria to sort the reviews: Most Relevant, Newest, Highest Rating, or Lowest Rating. Default is Most Relevant (qualityScore).
- Topic ID (topic_id) Filter reviews by a specific topic ID found inside the structured JSON response.
- Number of Results (num) Maximum number of reviews to return (1 to 20). Cannot be used on the initial page if neither next_page_token nor topic_id is set. Default is 10.
- Next Page Token (next_page_token) Token to retrieve the next page of results for pagination.
- Disable Caching (no_cache) Boolean flag to force fetching fresh results instead of cached ones. Cache expires after 1 hour. Default is false (allow cache). Cannot be used together with async.
- Async (async) Boolean flag to perform the search asynchronously. If true, results must be retrieved later via Search Archive API. Cannot be used with no_cache or on accounts with Ludicrous Speed enabled. Default is false.
- ZeroTrace Mode (zero_trace) Enterprise-only boolean flag to disable storing search parameters and metadata on SerpApi servers for privacy. Default is false.
- Output (output) Format of the final output: json (structured JSON, default) or html (raw HTML retrieved).
- JSON Restrictor (json_restrictor) Restricts fields returned in the JSON response, e.g., limiting to certain properties of the first few results.

Output

The node outputs a JSON object containing the Google Maps reviews data as returned by SerpApi. This includes:

  • Review details such as author name, rating, text, time, and any associated metadata.
  • Pagination tokens if more results are available.
  • Structured data that can be filtered or restricted using the JSON Restrictor property.

If the output format is set to html, the raw HTML content of the search result page is returned instead.

The node does not output binary data.

Dependencies

  • Requires an active SerpApi account with a valid API key credential configured in n8n.
  • Internet access to call SerpApi endpoints.
  • No additional external dependencies beyond the SerpApi service.

Troubleshooting

  • Missing Data ID or Place ID: The node requires either a Data ID or Place ID to identify the place. Ensure one of these is provided; otherwise, the request will fail.
  • Invalid API Key or Credential Issues: Authentication errors occur if the API key is missing or invalid. Verify the API key credential configuration.
  • Rate Limits or Quotas Exceeded: SerpApi enforces usage limits. If you hit rate limits, consider upgrading your plan or reducing request frequency.
  • Conflicting Parameters: no_cache and async cannot be used together. Using both will cause errors.
  • Pagination Errors: When using next_page_token, ensure it is valid and corresponds to the previous query.
  • Unsupported Language Codes: Use only supported language codes for the hl parameter to avoid unexpected results.
  • Async Mode Restrictions: Async mode cannot be used with Ludicrous Speed accounts and requires separate retrieval of results.

Links and References

Discussion