Google Search API
Actions7
- Image Actions
- News Actions
- Scholar Actions
- Search Actions
- Shopping Actions
- Video Actions
Overview
This node integrates with the Google Search API (via Serper.dev) to perform web search queries. It allows users to send search requests and retrieve structured search results programmatically within n8n workflows. This is useful for automating data gathering, monitoring trends, or enriching datasets with real-time search information.
Typical use cases include:
- Performing automated web searches based on dynamic input queries.
- Extracting search result data for analysis or reporting.
- Integrating search capabilities into larger automation workflows without manual intervention.
For example, a user can input a search query like "latest technology news" and receive a list of relevant web pages, which can then be processed further in the workflow.
Properties
| Name | Meaning |
|---|---|
| Page | Page number for paginated results (e.g., 1, 2, 3...) |
| Query | The search query string to look up |
| Results | Number of results to return; options: 10, 20, 40, 60, 80, 100 |
| Country | Country code to localize the search (e.g., "us" for United States, "de" for Germany) |
| Language | Language code for the search results (e.g., "en" for English, "fr" for French) |
| Autocorrect | Boolean flag to enable or disable autocorrect on the search query |
Output
The node outputs a JSON array where each item corresponds to an individual search result returned by the API. The exact structure depends on the API response but generally includes fields such as titles, snippets, URLs, and other metadata related to each search result.
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 endpoints.
- 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 country or language codes might yield unexpected or no results.
- Network connectivity problems can cause HTTP request failures.
Error messages:
- Errors from the API are caught and returned 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 active.
- Check the spelling and validity of country and language codes.
- Use smaller result counts or fewer requests to avoid rate limiting.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- Serper.dev API Documentation
- Google Search API Concepts
- n8n HTTP Request Node Documentation (for understanding HTTP calls)
This summary covers the "Search" resource with the "Web Search" operation specifically, reflecting the properties and behavior relevant to that combination.