Actions85
- Account Actions
- Calendar Actions
- Email Actions
- LinkedIn Actions
- Close Job Posting
- Create Job Posting
- Download Applicant Resume
- Edit Job Posting
- Endorse Skill
- Get Company Profile
- Get Hiring Project by ID
- Get Hiring Projects
- Get Inmail Balance
- Get Job Applicant
- Get Job Applicants
- Get Job Offer
- Get Job Postings
- Get Raw Data
- Perform Action on Member
- Publish Job Posting
- Search
- Search Parameters
- Solve Job Publishing Checkpoint
- Messaging Actions
- Post Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Unipile API, specifically providing operations related to various resources including LinkedIn. The "Get Job Applicant" operation under the LinkedIn resource retrieves detailed information about a specific job applicant using their Applicant ID and the associated Account ID.
Common scenarios for this node include automating recruitment workflows by fetching applicant data directly from LinkedIn via Unipile, integrating applicant information into HR systems, or triggering follow-up actions based on applicant details.
For example, a user might use this node to automatically pull applicant profiles after a job posting closes, enabling seamless processing of candidate data without manual lookup.
Properties
| Name | Meaning |
|---|---|
| Applicant ID | The unique identifier of the job applicant whose information you want to retrieve. |
| Account ID | The identifier of the LinkedIn account associated with the job posting or applicant. |
Output
The node outputs JSON data containing the detailed information of the requested job applicant as returned by the Unipile API. This typically includes fields such as applicant profile details, application status, and any other metadata provided by LinkedIn through Unipile.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Unipile API.
- Needs an API key credential configured in n8n to authenticate requests to Unipile.
- The base URL for the API is dynamically set from the credential's DSN (Data Source Name).
Troubleshooting
- Missing or invalid Applicant ID or Account ID: Ensure both IDs are correctly provided and correspond to existing entities in LinkedIn via Unipile.
- Authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Network or API errors: Check connectivity to the Unipile service and confirm the API endpoint is reachable.
- Empty or unexpected response: Confirm that the applicant exists and that the account ID matches the correct LinkedIn account.
Links and References
- Unipile API Documentation (general reference for API capabilities)
- LinkedIn Developer Documentation (for understanding LinkedIn data structures)