Pearch icon

Pearch

Search for candidates using Pearch API with automatic result waiting

Overview

This node integrates with the Pearch API to perform candidate searches based on user-defined queries. It submits a search request and then waits for the results asynchronously by polling the search status until completion or timeout. This is useful in recruitment automation workflows where you want to programmatically find candidates matching specific criteria, including advanced AI-powered insights and scoring.

Common scenarios include:

  • Searching for candidates with particular skills or experience (e.g., "python developer with Django experience").
  • Automating talent sourcing pipelines that require waiting for comprehensive search results.
  • Enriching candidate data with emails, phone numbers, and AI-driven profile scores.
  • Prioritizing fresh or recently updated candidate profiles.

Practical example:
You could use this node to submit a search query for "frontend developer with React experience," wait for the search to complete, and then process the returned candidate profiles with enriched contact details and AI insights for further evaluation or outreach.

Properties

Name Meaning
Query Search query string describing desired candidate profile (e.g., "python developer with Django experience").
Limit Maximum number of candidate results to return (minimum 1).
Search Type Type of search:
- Fast: Quick search with basic results.
- Pro: Comprehensive professional search with detailed results.
Insights Include AI-powered insights about candidates (true/false).
High Freshness Prioritize recently updated candidate profiles (true/false).
Show Emails Include candidate email addresses in the results (true/false).
Show Phone Numbers Include candidate phone numbers in the results (true/false).
Profile Scoring Include AI-powered profile matching scores (true/false).
Max Wait Time (Seconds) Maximum time to wait for search completion, between 10 seconds and 1 hour (default 600s).
Polling Interval (Seconds) How often to check the search status, between 2 and 60 seconds (default 15s).

Output

The node outputs an array of items, each containing a json field with the full search status and results object returned from the Pearch API once the search completes successfully.

The output JSON structure includes:

  • Task ID and search metadata.
  • Status of the search.
  • Candidate results with optional fields depending on input parameters (emails, phone numbers, AI insights, profile scores).
  • Any additional data provided by the Pearch API response.

No binary data output is produced by this node.

Dependencies

  • Requires an active Pearch API credential with:
    • Base URL for the API endpoint.
    • API key for authorization.
  • The node makes HTTP requests to the Pearch API endpoints /v2/search/submit and /v2/search/status/{task_id}.
  • Proper network connectivity to the Pearch API service is necessary.
  • The node uses n8n's built-in HTTP request helper and credential management.

Troubleshooting

  • Empty or missing Query: The node throws an error if the "Query" parameter is empty or whitespace. Ensure a valid search query is provided.
  • Missing credentials: Errors occur if the API key or base URL are not configured in the credentials. Verify that the Pearch API credential is set up correctly.
  • Timeout waiting for results: If the search does not complete within the specified max wait time, an error is thrown. Increase the "Max Wait Time" or check the Pearch API status.
  • Search failure status: If the API returns a failed or error status during polling, the node throws an error indicating the failure. Check the query validity and API limits.
  • Polling interval too short or long: Setting very low polling intervals may cause unnecessary load; too high may delay result retrieval. Use recommended defaults or adjust as needed.
  • Network issues: Connectivity problems to the Pearch API will cause HTTP request failures. Ensure stable internet access and correct API endpoint.

Links and References

Discussion