Actions19
- User Actions
- Email Actions
- Post Actions
- Company Actions
- Search Actions
- Google Actions
- Group Actions
Overview
This node performs a Google search operation via an external API service. It allows users to submit a search query and retrieve a specified number of search results from Google. This is useful for automating web search tasks, gathering information, or integrating search results into workflows.
Typical use cases include:
- Automatically searching for topics or keywords relevant to your business.
- Gathering URLs or snippets related to a specific query.
- Integrating Google search results into data pipelines or reports.
For example, you could use this node to search for "python fastapi" and get the top 10 results, which can then be processed or filtered further in your workflow.
Properties
| Name | Meaning |
|---|---|
| Query | The search query string to send to Google (e.g., "python fastapi"). |
| Count | Maximum number of search results to return. Allowed range: 1 to 20. |
| Timeout | Timeout duration in seconds for the search request before it fails. Default is 300 sec. |
Output
The node outputs JSON data containing the search results returned by the external API. The structure typically includes an array of search result items with details such as titles, URLs, snippets, and other metadata related to each search hit.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authentication with the external Horizon Data Wave LinkedIn API service.
- The node sends HTTP POST requests to
https://api.horizondatawave.ai/api/google/search. - Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
- Timeouts: If the search takes longer than the specified timeout, the request may fail. Increase the timeout property if needed.
- Invalid Query: An empty or malformed query string may cause errors or no results.
- API Errors: The node surfaces detailed error messages from the API including HTTP status codes and error headers. Common issues include invalid credentials, rate limits, or malformed requests.
- Rate Limits: Excessive requests may lead to throttling or token point exhaustion. Monitor usage and adjust frequency accordingly.
- Network Issues: Ensure that the n8n instance has internet access to reach the external API endpoint.
If an error occurs, the node returns detailed information including HTTP status, API error message, request ID, execution time, and token points used, aiding in diagnosis.
Links and References
- Google Search API Documentation (general reference for Google search APIs)
- Horizon Data Wave API (base URL for the used API service; documentation may require access)
Note: The above summary is based on static analysis of the provided source code and input properties. Runtime behavior depends on the external API responses and configured credentials.