Actions36
- Authentication Actions
- Profile Actions
- Company Actions
- Network Actions
- Message Actions
- Post Actions
- Recruiter Actions
- Data Actions
Overview
The Linkup API for LinkedIn node enables automation of LinkedIn Recruiter job postings, specifically allowing users to publish or close job postings on LinkedIn Recruiter via the Linkup API. This node is useful for recruiters and HR professionals who want to programmatically manage their job postings without manually interacting with LinkedIn’s interface.
For the Publish Job operation under the Recruiter resource, the node sends a request to publish an existing job posting identified by its unique Job ID. This can be part of automated workflows that activate job listings once they are ready or after certain conditions are met (e.g., budget approval, internal review).
Practical Examples
- Automatically publish a job posting when a new position opens.
- Integrate with other HR systems to trigger job publication based on candidate pipeline status.
- Schedule job postings to go live at specific times using n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Job ID | Unique identifier of the job posting to be published or closed. |
| Country Code | Country code used for proxy selection to route requests appropriately (e.g., FR, US, UK). |
| Timeout | Request timeout in milliseconds (default 30000 ms). |
| Retry Count | Number of retry attempts if the request fails (default 3). |
These properties are grouped into two collections:
- Linkup Parameters (
publishCloseJobParams): ContainsJob IDandCountry Code. - Advanced Options (
additionalFields): ContainsTimeoutandRetry Count.
Output
The node outputs JSON data containing the response from the Linkup API for the publish job request. The output includes:
- The full API response fields as returned by the Linkup service.
- A
_debugobject with:requestBody: The JSON body sent in the API request.requestHeaders: HTTP headers used.endpoint: The API endpoint URL called.apiResponse: Raw response from the API.
- Metadata
_metaincluding:resource: The resource name ("recruiter").operation: The operation name ("publishJob").timestamp: ISO timestamp of execution.nodeVersion: Version of the node implementation.
If an error occurs, the output JSON will contain an error field with the error message, along with resource, operation, and timestamp metadata.
The node does not output binary data.
Dependencies
- Requires an API key credential for the Linkup API to authenticate requests.
- The node uses the Linkup API base URL:
https://api.linkupapi.com/v1. - Proper configuration of the API key credential in n8n is necessary.
- Optional country code parameter helps select appropriate proxy routing for requests.
Troubleshooting
- Missing API Key Error: If the API key credential is not configured or invalid, the node throws an error indicating the missing API key. Ensure the API key is set up correctly in n8n credentials.
- Invalid Job ID: Providing an incorrect or non-existent Job ID may cause the API to return an error. Verify the Job ID before publishing.
- Timeouts: Requests may time out if the server is slow or network issues occur. Adjust the
Timeoutproperty or increase theRetry Countto handle transient failures. - Country Code Issues: Using an unsupported or incorrect country code might lead to proxy routing errors. Use valid country codes like "FR", "US", "UK", etc.
- API Response Errors: The node surfaces API errors in the output JSON's
errorfield. Review the API documentation or logs for detailed troubleshooting.
Links and References
- Linkup API Documentation — Official site to create accounts and get API keys.
- LinkedIn Recruiter Help — For understanding job posting management on LinkedIn.
- n8n Documentation on Creating Custom Nodes — For extending or debugging nodes.
This summary covers the static analysis of the Linkup node’s Recruiter > Publish Job operation, focusing on input parameters, output structure, dependencies, and common troubleshooting points.