Google Search API icon

Google Search API

Integrate with Google Search API (Serper.dev API) for search functionalities. Powered by CloudFly

Actions7

Overview

This node integrates with the Google Search API (via Serper.dev) to perform various types of searches, including web, image, video, news, shopping, and scholarly article searches. Specifically, the "Scholar Search" operation allows users to search for scholarly articles and academic papers using a query string.

Typical use cases include:

  • Researchers or students looking to find academic papers related to a specific topic.
  • Automating literature reviews by fetching scholarly articles programmatically.
  • Integrating scholarly search results into workflows for data analysis or reporting.

For example, you could input a query like "machine learning in healthcare" and retrieve a list of relevant scholarly articles, including metadata such as titles, authors, and publication details.

Properties

Name Meaning
Page Page number for paginated results
Query The search query string for finding scholarly articles
Results Number of results to return; options: 10, 20, 40, 60, 80, 100
Country Country code to localize the search; many country options available (e.g., US, UK, DE)
Language Language code to specify the language of the search results (e.g., en, fr, de, zh-cn)
Autocorrect Boolean flag to enable or disable autocorrect on the search query

Output

The node outputs an array of JSON objects representing the search results from the scholarly search. Each item corresponds to one scholarly article or result returned by the API. The exact structure depends on the API response but typically includes fields such as title, authors, publication source, snippet, and URL.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Serper.dev Google Search API.
  • The node uses HTTP POST requests to the Serper.dev endpoint https://google.serper.dev/schollar.
  • Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

  • Common issues:
    • Invalid or missing API key credential will cause authentication errors.
    • Exceeding API rate limits may result in request failures.
    • Incorrect parameter values (e.g., unsupported country or language codes) might lead to empty or error responses.
  • Error messages:
    • Errors thrown by the API are caught and can be output as error objects if "Continue On Fail" is enabled.
    • Typical errors include network issues, invalid credentials, or malformed requests.
  • Resolution tips:
    • Verify that the API key credential is correctly set up and active.
    • Check the spelling and validity of query parameters.
    • Use smaller result counts or fewer pages to avoid hitting rate limits.

Links and References

Discussion