Linkup API for LinkedIn icon

Linkup API for LinkedIn

Automate LinkedIn with Linkup

Actions36

Overview

The node integrates with the Linkup API to automate LinkedIn post-related activities. Specifically, the Search Posts operation allows users to search LinkedIn posts based on various criteria such as keywords, post type, date, sorting preferences, and more. This is useful for social media managers, recruiters, marketers, or anyone looking to monitor or analyze LinkedIn content relevant to their interests or business.

Practical examples:

  • Searching for posts containing specific keywords related to your industry.
  • Filtering posts by geographic location or company.
  • Retrieving recent posts sorted by date or popularity.
  • Gathering posts of a certain type (e.g., articles, shares) for content curation.

Properties

Name Meaning
Keyword Search keyword(s) to filter posts.
Location(s) Geographic locations to filter posts by, separated by semicolons (;).
Company(ies) LinkedIn company URLs to filter posts by, separated by semicolons (;).
School(s) LinkedIn school URLs to filter posts by, separated by semicolons (;).
Network Connection level filter: F = 1st degree, S = 2nd degree, O = outside network.
Sector(s) Business sectors to filter posts by, separated by semicolons (;).
Company Size Filter posts by company size range.
First Name Filter posts by author's first name.
Last Name Filter posts by author's last name.
Title/Position Filter posts by author's title or position.
Show Invitation Status Boolean flag to include invitation status for each profile in results. Defaults to true.
Post Type Type of post to search (e.g., article, share).
Sort By Criteria to sort posts (e.g., date, relevance).
Post Date Filter posts by date.
LinkedIn URL (search) Specific LinkedIn URL to use as a search base.
Number of Results Number of posts to retrieve per page/request. Default is 10.
Start Page The first page number to retrieve. Default is 1.
End Page The last page number to retrieve. Default is 1.
Country Code Country code used for proxy selection (e.g., FR for France, US for United States). Default is FR.

Advanced Options

Name Meaning
Timeout Request timeout in milliseconds. Default is 30000 (30 seconds).
Retry Count Number of retries on failure. Default is 3.

Output

The output JSON contains the response from the Linkup API for the searched posts. It includes:

  • The main data returned by the API matching the search criteria.
  • A _debug object with:
    • requestBody: The JSON body sent in the API request.
    • requestHeaders: HTTP headers used.
    • endpoint: The API endpoint called.
    • apiResponse: Raw API response.
  • A _meta object with metadata:
    • resource: The resource used (post).
    • operation: The operation performed (searchPosts).
    • timestamp: ISO timestamp of execution.
    • nodeVersion: Version of the node.

If an error occurs, the output JSON will contain an error field describing the issue along with resource, operation, and timestamp.

This node does not output binary data.

Dependencies

  • Requires an API key credential for the Linkup API.
  • The node uses the Linkup API endpoint at https://api.linkupapi.com/v1.
  • Requires proper configuration of credentials including API key and optionally LinkedIn email/password for some operations.
  • Proxy country code can be specified for regional routing.

Troubleshooting

  • Missing API Key Error: If the API key is not configured or invalid, the node throws an error indicating the missing API key. Ensure you have set up the Linkup API key credential correctly.
  • Timeouts: Requests may timeout if the API is slow or network issues occur. Adjust the "Timeout" advanced option if needed.
  • Invalid Parameters: Providing incorrect or malformed parameters (e.g., invalid LinkedIn URLs or JSON strings) may cause errors. Validate inputs before running.
  • Rate Limits: The Linkup API may enforce rate limits; repeated failures might indicate hitting these limits. Use retry count settings cautiously.
  • Country Code Issues: Using unsupported or incorrect country codes for proxy selection may lead to failed requests.

Links and References

Discussion