PersonalFinder icon

PersonalFinder

Interact with PersonalFinder API - Complete integration for recruitment and job matching

Job Seeker (Arbeitsuchende) → Get Filtered

AI-generated

Overview

This node interacts with the PersonalFinder API to retrieve filtered job seeker data based on various criteria. It allows users to specify filters such as first name, last name, email, phone, city, ZIP code, job branch, nationality, and work permit type to narrow down the list of job seekers. Additionally, users can control the number of results returned and the offset for pagination. This operation is useful for recruitment professionals or HR teams who want to search and manage job seeker profiles efficiently by applying specific filters to find suitable candidates.

Use Case Examples

  1. A recruiter wants to find job seekers located in a specific city with a particular job branch to target candidates for a new opening.
  2. An HR team filters job seekers by nationality and work permit type to comply with legal hiring requirements.
  3. A hiring manager retrieves a limited number of job seeker profiles starting from a certain offset to paginate through large datasets.

Properties

Name Meaning
Filters Collection of filter criteria to narrow down job seekers based on attributes like first name, last name, email, phone, city, ZIP code, job branch, nationality, and work permit type.
Limit Maximum number of results to return.
Offset Number of results to skip for pagination.

Output

JSON

  • json - The filtered list of job seekers returned from the PersonalFinder API, including their details matching the specified filters.

Dependencies

  • Requires an API key credential for PersonalFinder API authentication.

Troubleshooting

  • Ensure that the API credentials are correctly configured and valid to avoid authentication errors.
  • If no results are returned, verify that the filter criteria are correctly specified and match existing job seeker data.
  • Pagination parameters (limit and offset) should be set appropriately to avoid empty result sets.
  • Handle API rate limits or network issues that might cause request failures.

Links

Discussion