Outscraper icon

Outscraper

Interact with Outscraper API

Actions49

Overview

The Google Search - Search Events operation in this node allows users to perform event-related searches using the Outscraper API. It enables querying for events based on a search term, with options to control pagination, language, region, date filtering, and asynchronous execution. This is useful for gathering event data such as concerts, conferences, or local happenings from Google Search results.

Practical examples include:

  • Finding upcoming tech conferences in a specific country.
  • Searching for music festivals happening within the past month.
  • Collecting event data asynchronously for later processing via webhook callbacks.

Properties

Name Meaning
Query The search query string to find relevant events (e.g., "tech conferences 2024").
Pages Per Query Number of pages of results to retrieve per query (controls result volume).
Async Request Whether to make the request asynchronously; if true, results will be delivered via webhook callback.
Webhook URL to which Outscraper will send a POST request once the asynchronous task is finished.
Language Language code for the search results (e.g., "en" for English, "fr" for French).
Additional Fields A collection of optional parameters:
- Date Range Filter results by time period: Past Hour, Past 24 Hours, Past Week, Past Month, Past Year.
- Fields Comma-separated list of specific fields to return in the response.
- Region Country code to localize results (e.g., "us", "uk", "fr").
- Skip Number of results to skip for pagination purposes.
- UULE Parameter Google UULE parameter to encode a specific location for more precise geotargeting.

Output

The node outputs JSON data containing the search results for events matching the query and filters specified. The structure typically includes event details such as titles, dates, locations, descriptions, and URLs. If the request is asynchronous, the output may initially contain task status information, with final results sent to the provided webhook URL.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active Outscraper API key credential configured in n8n.
  • The node sends requests to the Outscraper API endpoint specified in credentials.
  • For asynchronous requests, a publicly accessible webhook URL must be provided to receive callbacks.

Troubleshooting

  • Common issues:
    • Missing or invalid API key will cause authentication errors.
    • Incorrect webhook URL or network issues can prevent receiving asynchronous results.
    • Exceeding page limits or rate limits imposed by Outscraper API may result in errors or incomplete data.
  • Error messages:
    • Authentication failures: Verify API key correctness and permissions.
    • Timeout or connection errors: Check network connectivity and webhook accessibility.
    • Invalid parameter errors: Ensure all required properties are set correctly and values conform to expected formats.

Links and References

Discussion