PersonalFinder icon

PersonalFinder

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

Matching & Swipe → Calculate Matches for Multiple Job Seekers (Async)

AI-generated

Overview

This node integrates with the PersonalFinder API to perform batch matching calculations for multiple job seekers asynchronously. It collects job seeker IDs from the input, processes them in the background, and initiates a matching process on the server that continues independently of the node's execution. This is useful for scenarios where you want to trigger AI-based job matching for many job seekers at once without waiting for the process to complete, such as in recruitment automation workflows.

Use Case Examples

  1. Trigger batch matching for a list of job seeker IDs obtained from a previous node.
  2. Start an asynchronous matching process for multiple job seekers to update their match scores in the background.

Properties

Name Meaning
Job Seeker IDs Comma-separated list or single job seeker IDs to calculate matches for. The process runs asynchronously in the background and does not wait for completion.

Output

JSON

  • status - Status of the batch matching process (e.g., 'started').
  • message - Informational message about the batch matching initiation.
  • processed_ids - Array of job seeker IDs that were processed.
  • total_count - Total number of job seekers processed.
  • async - Boolean indicating the process runs asynchronously in the background.
  • note - Additional note explaining that the matching runs on the server and the node does not wait for completion.

Dependencies

  • PersonalFinder API with API key credential

Troubleshooting

  • Ensure the 'Job Seeker IDs' input is correctly formatted as comma-separated numbers or single IDs; invalid or missing IDs will cause errors.
  • If the node throws 'No valid Job Seeker IDs found' error, verify that the input data contains valid numeric IDs.
  • Network or API errors during the asynchronous request will be logged but do not stop the node execution; check API connectivity and credentials if matching does not start.

Links

Discussion