Linkup API for LinkedIn icon

Linkup API for LinkedIn

Automate LinkedIn with Linkup

Actions36

Overview

This node integrates with the Linkup API to automate LinkedIn Recruiter job posting management. Specifically, the Get Job Posts operation retrieves a list of job postings from LinkedIn Recruiter associated with your account.

Typical use cases include:

  • Automatically fetching and monitoring active job posts for recruitment campaigns.
  • Integrating job post data into HR dashboards or applicant tracking systems.
  • Automating workflows that trigger actions based on new or updated job postings.

For example, a recruiter could use this node to regularly pull all current job postings and then notify hiring managers or update internal databases without manual intervention.

Properties

Name Meaning
Years of Experience Required years of experience filter for candidates (used in candidate queries, not job posts).
Sort Type Sorting criteria for candidates (not applicable directly to job posts).
Sort Order Sort order direction: ASC (ascending) or DESC (descending) (candidate-related).
Ratings Filter by ratings (candidate-related).
Start Starting point for pagination (Recruiter context).
Number of Results Number of job posts to retrieve per request (default 10).
Start Page First page number to retrieve (pagination).
End Page Last page number to retrieve (pagination).
Country Code Country code for proxy selection and localization (e.g., FR, US, UK). Defaults to "FR".
Timeout Request timeout in milliseconds (default 30000 ms).
Retry Count Number of retries on failure (default 3).

Note: Some properties like Years of Experience, Sort Type, Sort Order, and Ratings are more relevant to candidate queries but are part of the same parameter collection.

Output

The node outputs JSON data containing the response from the Linkup API's /recruiter/job-posts endpoint. The output includes:

  • The list of job posts matching the query parameters.
  • Metadata such as resource name ("recruiter"), operation ("getJobPosts"), timestamp, and node version.
  • A debug section showing the exact request body sent, headers used, endpoint URL, and raw API response for troubleshooting.

No binary data is returned by this operation.

Example output structure (simplified):

{
  "json": {
    "_debug": {
      "requestBody": { /* parameters sent */ },
      "requestHeaders": { /* HTTP headers */ },
      "endpoint": "/recruiter/job-posts",
      "apiResponse": { /* raw API response with job posts */ }
    },
    "jobPosts": [
      {
        "id": "12345",
        "title": "Software Engineer",
        "location": "Paris, France",
        "status": "Open",
        // other job post details...
      }
      // more job posts...
    ],
    "_meta": {
      "resource": "recruiter",
      "operation": "getJobPosts",
      "timestamp": "2024-06-xxTxx:xx:xx.xxxZ",
      "nodeVersion": "1.2.31"
    }
  },
  "pairedItem": {
    "item": 0
  }
}

Dependencies

  • Requires an API key credential for the Linkup API.
  • The node uses HTTP POST requests to the Linkup API endpoint https://api.linkupapi.com/v1/recruiter/job-posts.
  • Optional country code parameter controls proxy selection and localization.
  • Configurable timeout and retry count for network robustness.

Troubleshooting

  • Missing API Key Error: If the API key credential is not configured, the node will throw an error indicating the missing API key. Ensure you have set up the required API authentication token in the node credentials.
  • Timeouts or Network Errors: Adjust the "Timeout" and "Retry Count" advanced options if experiencing intermittent network issues.
  • Invalid Parameters: Passing invalid or malformed parameters (e.g., non-numeric pagination values) may cause API errors. Validate input fields carefully.
  • Empty Results: If no job posts are returned, verify that the account has active job postings and that filters like country code or pagination are correctly set.

Links and References

Discussion