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 integrates with the Unipile API to perform various operations, including creating a LinkedIn job posting. Specifically, the "Create Job Posting" operation under the LinkedIn resource allows users to submit job postings directly to LinkedIn via the Unipile service. This is useful for automating recruitment workflows, enabling HR teams or recruiters to programmatically post jobs without manual entry on LinkedIn's platform.
Practical examples include:
- Automatically posting new job openings from an internal HR system.
- Syncing job listings across multiple platforms by using Unipile as a central hub.
- Scheduling job posts in bulk based on predefined templates or JSON payloads.
Properties
| Name | Meaning |
|---|---|
| Body (JSON) | The JSON object representing the job posting details to be sent to LinkedIn via Unipile. This should contain all necessary fields as per LinkedIn's job posting requirements wrapped in JSON format. |
Output
The node outputs JSON data representing the response from the Unipile API after attempting to create the LinkedIn job posting. This typically includes confirmation of the job post creation, identifiers, status messages, or error details if the operation failed.
If the node supports binary data output, it would generally relate to attachments or media associated with the job post, but this is not indicated in the provided code snippet.
Dependencies
- Requires an active connection to the Unipile API, authenticated via an API key credential.
- The base URL for API requests is configured dynamically from the user's credentials.
- Proper permissions and API access rights on both Unipile and LinkedIn sides are necessary to successfully create job postings.
Troubleshooting
Common Issues:
- Invalid or incomplete JSON in the "Body (JSON)" property can cause request failures.
- Missing or incorrect API credentials will prevent authentication.
- Insufficient permissions on LinkedIn or Unipile may result in authorization errors.
- Network connectivity issues between n8n and the Unipile API endpoint.
Error Messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials.
- Validation errors from the API often point to malformed JSON or missing required fields in the job posting body.
- Timeout or network errors suggest connectivity problems; check internet access and API availability.
Links and References
- Unipile API Documentation (general reference for API capabilities)
- LinkedIn Job Posting Guidelines (for required job post fields and formats)
- n8n documentation on Creating Custom Nodes