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 across multiple resources, including LinkedIn. Specifically, for the LinkedIn resource and the "Close Job Posting" operation, it allows users to close an active job posting on LinkedIn by specifying the job and account details. This is useful in recruitment workflows where a job vacancy has been filled or is no longer available, enabling automation of job lifecycle management directly from n8n.
Practical examples:
- Automatically closing a LinkedIn job posting once a candidate is hired.
- Integrating with HR systems to update job statuses without manual intervention.
- Scheduling job closure based on external triggers or events.
Properties
| Name | Meaning |
|---|---|
| Job ID | The unique identifier of the LinkedIn job posting that you want to close. |
| Account ID | The LinkedIn account identifier under which the job posting exists. |
| Service | The service parameter sent as a query string; likely specifies the type or context of the request (exact meaning depends on API). |
Output
The node outputs JSON data representing the response from the Unipile API after attempting to close the specified LinkedIn job posting. This typically includes confirmation of the job closure status or any error messages returned by the API.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for the API is configured via credentials.
- Proper configuration of the LinkedIn account and job identifiers is necessary.
- Network access to the Unipile API endpoint.
Troubleshooting
- Invalid Job ID or Account ID: If these IDs are incorrect or do not exist, the API will likely return an error. Verify the IDs before running the node.
- Authentication Errors: Ensure the API key credential is valid and has the necessary permissions.
- Service Parameter Issues: If the
servicequery parameter is required by the API but missing or incorrect, the request may fail. - API Connectivity: Network issues or incorrect base URL configuration can cause failures.
- Error Messages: The node will relay error messages from the API; check those messages for clues on misconfiguration or invalid inputs.
Links and References
- Unipile API Documentation (general reference, replace with actual if available)
- LinkedIn Job Posting API (for understanding job posting concepts)
- n8n documentation on Creating Custom Nodes