Outscraper icon

Outscraper

Interact with Outscraper API

Actions49

Overview

The Google Search - Search Careers operation in this node allows users to perform career-related searches using the Outscraper API. It is designed to query job listings and career opportunities based on a search term, returning structured data about available positions. This can be useful for automating job market research, aggregating job postings, or integrating career search functionality into workflows.

Practical examples include:

  • Automatically fetching recent job openings for a specific role or skill set.
  • Aggregating career opportunities from multiple locations or languages.
  • Filtering job results by date range or region to target relevant markets.

Properties

Name Meaning
Query The search query string specifying the job title, skills, or keywords to find relevant careers.
Pages Per Query Number of pages of results to retrieve per query (pagination limit).
Async Request Whether to make the request asynchronously (true/false).
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 Collection of optional parameters:
- Date Range Filter results by date range: Past Hour, 24 Hours, Week, Month, Year.
- Fields Comma-separated list of specific fields to return in the response.
- Region Country code to localize search 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 careers matching the query. The structure typically includes an array of job listings with details such as job title, company, location, posting date, and other relevant metadata depending on requested fields.

If the request is asynchronous, the output may initially contain task status information, and the final results will be sent to the specified webhook URL.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active Outscraper API key credential configured in n8n.
  • Internet access to call the Outscraper API endpoint.
  • Optional webhook URL if asynchronous requests are used.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Incorrect or unsupported language or region codes may result in empty or irrelevant results.
    • Asynchronous requests require a valid webhook URL; otherwise, results cannot be retrieved after task completion.
    • Pagination parameters (pagesPerQuery, skip) must be within allowed limits to avoid errors.
  • Error messages:

    • Authentication failures: Check that the API key is correctly set and has necessary permissions.
    • Rate limiting or quota exceeded: Reduce request frequency or upgrade API plan.
    • Invalid parameter values: Verify that all input properties conform to expected formats and supported options.

Links and References

Discussion