Actions36
- Authentication Actions
- Profile Actions
- Company Actions
- Network Actions
- Message Actions
- Post Actions
- Recruiter Actions
- Data Actions
Overview
The "Close Job" operation in the Recruiter resource of this node allows users to close a LinkedIn Recruiter job posting via the Linkup API. This is useful for recruiters or HR professionals who want to automate the management of their job postings on LinkedIn, specifically to mark a job as no longer accepting applications.
Typical scenarios include:
- Automatically closing job postings once a position is filled.
- Managing job lifecycle programmatically within recruitment workflows.
- Integrating with other automation tools to update job statuses without manual intervention.
Example use case:
- After receiving enough qualified candidates, a recruiter can trigger this node to close the job posting on LinkedIn, ensuring it is no longer visible to applicants.
Properties
| Name | Meaning |
|---|---|
| Job ID | Unique identifier of the job posting to be closed. |
| Country Code | Country code used for proxy selection (e.g., FR for France, US for United States). |
| Timeout | Request timeout duration in milliseconds (default 30000 ms). |
| Retry Count | Number of retry attempts if the request fails (default 3). |
Output
The node outputs JSON data containing the response from the Linkup API after attempting to close the job posting. The output includes:
_debug: Debug information including the request body sent, request headers, endpoint URL, and raw API response.- The API response fields as returned by the Linkup service.
_meta: Metadata about the executed operation such as resource name ("recruiter"), operation name ("closeJob"), timestamp of execution, and node version.pairedItem: Indicates which input item the output corresponds to.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Linkup API.
- The node uses the Linkup API endpoint at
https://api.linkupapi.com/v1/recruiter/close-job. - Proper configuration of the API key credential in n8n is necessary.
- Optionally, country codes are used to select proxies for requests.
Troubleshooting
- Missing API Key: If the API key credential is not configured or invalid, the node will throw an error indicating the missing API key. Ensure the API key is set up correctly in the node credentials.
- Invalid Job ID: Providing an incorrect or non-existent Job ID may result in API errors or failure to close the job. Verify the Job ID before running the node.
- Timeouts: Network issues or slow responses might cause timeouts. Adjust the "Timeout" property if needed.
- API Rate Limits or Errors: The node retries failed requests up to the configured retry count. Persistent failures may indicate API limits or other issues; check API usage and credentials.
- Country Code Issues: Using unsupported or incorrect country codes may affect proxy routing and cause request failures.
Links and References
- Linkup API Documentation — Official site for API details and account creation.
- LinkedIn Recruiter Help — For understanding job posting lifecycle on LinkedIn.
This summary focuses exclusively on the "Close Job" operation under the "Recruiter" resource based on the provided source code and properties.