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 supporting operations on multiple resources including LinkedIn. For the LinkedIn resource, the "Get Job Offer" operation retrieves detailed information about a specific job posting from LinkedIn using the Unipile service as an intermediary.
Typical use cases include:
- Automating retrieval of job posting details for HR or recruitment workflows.
- Integrating LinkedIn job data into other systems or dashboards.
- Enriching candidate management processes by fetching up-to-date job offer information.
Example: A recruiter can input a LinkedIn Job ID and Account ID to fetch the full job posting details automatically, avoiding manual lookup.
Properties
| Name | Meaning |
|---|---|
| Job ID | The unique identifier of the LinkedIn job posting to retrieve. |
| Account ID | The LinkedIn account identifier associated with the job posting. |
| Service | The service parameter required by the Unipile API to specify the LinkedIn service usage. |
Output
The node outputs JSON data representing the retrieved LinkedIn job posting details. This typically includes all relevant fields returned by the Unipile API for the specified job offer, such as job title, description, location, company info, and other metadata.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for the Unipile API.
- The node uses the base URL configured in the credentials to send requests.
- The Unipile API acts as a proxy/service layer to access LinkedIn data; thus, proper configuration and permissions on Unipile are necessary.
Troubleshooting
- Missing or invalid Job ID/Account ID: Ensure these required fields are correctly provided; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential for Unipile is valid and has appropriate permissions.
- Service parameter issues: The "service" property must be correctly set to target LinkedIn within Unipile; incorrect values may cause request failures.
- API connectivity problems: Check network connectivity and the correctness of the base URL in credentials.
- Unexpected API responses: Inspect the raw response for error messages from Unipile or LinkedIn to diagnose issues.
Links and References
- Unipile API Documentation (general reference for the API used)
- LinkedIn Developer Documentation (for understanding LinkedIn job posting data structure)