Unipile icon

Unipile

Interact with Unipile API

Overview

This node interacts with the LinkedIn service to retrieve job applicants for a specified job posting. It is useful in recruitment workflows where you want to automate fetching candidate data directly from LinkedIn job listings. For example, HR teams can use this node to pull applicant information into their internal systems or trigger further processing like screening or notifications.

Properties

Name Meaning
Job ID The unique identifier of the LinkedIn job posting for which to fetch applicants (required).
Account ID The LinkedIn account identifier associated with the job posting (required).
Additional Fields Optional parameters to refine the query:
- Cursor Pagination cursor to fetch subsequent pages of applicants.
- Keywords Filter applicants by keywords matching their profiles or applications.
- Limit Maximum number of applicants to return in one request.
- Ratings Filter applicants by one or more ratings, separated by commas.
- Service Specify the LinkedIn service dependency related to the applicant.

Output

The node outputs JSON data containing the list of job applicants retrieved from LinkedIn. This typically includes applicant details such as names, profiles, application status, and any metadata returned by LinkedIn's API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with LinkedIn via the Unipile API.
  • The node depends on the Unipile API endpoint configured through credentials.
  • Proper configuration of the LinkedIn account and job identifiers is necessary.
  • Network access to the Unipile API service must be available.

Troubleshooting

  • Missing or invalid Job ID or Account ID: The node requires these fields; ensure they are correctly provided.
  • API authentication errors: Verify that the API key credential is valid and has appropriate permissions.
  • Pagination issues: If many applicants exist, use the Cursor field to paginate results properly.
  • Filtering returns no results: Check keyword spelling, rating values, and service names for correctness.
  • Rate limiting or API errors: Monitor API usage limits and handle errors gracefully in your workflow.

Links and References

Discussion