Outscraper icon

Outscraper

Interact with Outscraper API

Actions52

Google Search → Search Events

AI-generated

Overview

This node interacts with the Outscraper API to perform Google Search specifically for searching events. It allows users to input a search query and customize the search with options such as the number of pages to return, language, region, date range, and more. It supports asynchronous requests and webhook callbacks for task completion notifications. This node is useful for scenarios where users want to programmatically retrieve event-related search results from Google, such as for market research, event tracking, or content aggregation.

Use Case Examples

  1. A marketing team wants to gather upcoming event information related to their industry by searching Google Events programmatically.
  2. An event aggregator platform uses this node to fetch event data from Google to populate their listings automatically.

Properties

Name Meaning
Query The search query string to find relevant events on Google.
Pages Per Query The number of pages of search results to return for the query.
Async Request Whether to make the search request asynchronously.
Webhook URL to which Outscraper will send a POST request once the asynchronous task is finished.
Language Language code to localize the search results (e.g., en, fr, es).
Additional Fields Additional optional parameters to refine the search, including date range, specific fields to return, region for localized results, number of results to skip, and Google UULE parameter for location encoding.
Request Options Node-level request options including batching, SSL certificate validation, proxy settings, and request timeout.

Output

JSON

  • results - Array of event search results returned from the Google Search via Outscraper API.

Dependencies

  • Outscraper API key credential

Troubleshooting

  • Ensure the Outscraper API key is valid and has permissions for Google Search resource.
  • If asynchronous requests are used, verify the webhook URL is correctly configured and accessible to receive callbacks.
  • Check network connectivity and proxy settings if requests fail or time out.
  • Adjust timeout and batching settings if large queries cause delays or failures.

Links

Discussion