Google Search API icon

Google Search API

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

Actions7

Overview

This node integrates with the Serper.dev Google Search API to perform video search queries. Specifically, the "Find Videos" operation under the "Video" resource allows users to search for videos based on a query string and various optional parameters such as page number, number of results, country, language, and autocorrect settings.

Common scenarios where this node is beneficial include:

  • Automating video content discovery workflows.
  • Aggregating video search results for analysis or display.
  • Integrating video search capabilities into custom applications or automation pipelines.

For example, you could use this node to find the latest tutorial videos about "JavaScript async programming" limited to 20 results from the United States in English.

Properties

Name Meaning
Page Page number for paginated results (e.g., 1, 2, 3...)
Query The search query string to find relevant videos (required)
Results Number of results to return; options: 10, 20, 40, 60, 80, 100
Country Country code to localize search results; many country codes available (e.g., "us" for USA)
Language Language code to specify the language of search results; many language options available (e.g., "en" for English)
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. Each item corresponds to a video found by the search query. The exact structure of each video object depends on the Serper.dev API response but typically includes metadata such as video title, URL, description, thumbnail, duration, and possibly other relevant details.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for the Serper.dev Google Search API.
  • The node makes authenticated HTTP POST requests to https://google.serper.dev/videos.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication errors.
    • Exceeding API rate limits may result in request failures.
    • Providing invalid country or language codes might lead to unexpected or empty results.
    • Network connectivity issues can cause request timeouts or failures.

  • Error messages:

    • Errors returned from the API are caught and can be output as error objects if "Continue On Fail" is enabled.
    • Typical error messages include authentication failures, invalid parameters, or server errors.

  • Resolution tips:

    • Verify that the API key credential is correctly set up and has sufficient permissions.
    • Check the spelling and validity of input parameters like country and language codes.
    • Use smaller result counts or fewer requests to avoid hitting rate limits.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion