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 activities related to posts. Specifically, the "Send Post Time Spent Signal" operation allows users to record the amount of time spent viewing a particular LinkedIn post. This can be useful for analytics, engagement tracking, or automating workflows based on user interaction duration with content.

Practical scenarios include:

  • Tracking how long a user or audience spends on specific LinkedIn posts.
  • Feeding time-spent data into marketing automation or CRM systems.
  • Enhancing engagement metrics beyond simple likes or comments.

Properties

Name Meaning
LinkedIn Post URL (postUrl) The URL of the LinkedIn post to which the time spent signal applies. Example: https://www.linkedin.com/feed/update/xxx
Duration (seconds) (duration) The number of seconds spent viewing the post. Default is 30 seconds.
Start Time (timestamp) (durationStartTime) Unix timestamp in milliseconds indicating when the viewing started. Optional.
Country Code (country) Country code used for proxy selection or regional targeting (e.g., FR, US, UK). Defaults to "FR".

Additionally, under Advanced Options:

Name Meaning
Timeout Request timeout in milliseconds. Default is 30000 ms.
Retry Count Number of retries on failure. Default is 3.

Output

The node outputs JSON data containing:

  • The API response from the Linkup service regarding the time spent signal submission.
  • A _debug object with details about the request body, headers, endpoint, and raw API response for troubleshooting.
  • Metadata including resource name ("post"), operation name ("timeSpent"), timestamp of execution, and node version.
  • The output is paired with the input item index for traceability.

No binary data is produced by this operation.

Example output structure (simplified):

{
  "json": {
    "_debug": {
      "requestBody": { /* sent parameters */ },
      "requestHeaders": { /* HTTP headers */ },
      "endpoint": "/posts/time-spent",
      "apiResponse": { /* API response data */ }
    },
    /* ... actual API response fields ... */
    "_meta": {
      "resource": "post",
      "operation": "timeSpent",
      "timestamp": "2024-06-xxTxx:xx:xx.xxxZ",
      "nodeVersion": "1.2.31"
    }
  },
  "pairedItem": {
    "item": 0
  }
}

Dependencies

  • Requires an API key credential for the Linkup API to authenticate requests.
  • The node uses the Linkup API endpoint at https://api.linkupapi.com/v1/posts/time-spent.
  • Proper configuration of the API key credential in n8n is necessary.
  • Optionally, country codes can be specified for proxy routing or regional settings.

Troubleshooting

  • Missing API Key Error: If the API key is not configured, the node throws an error prompting to set up credentials.
  • Invalid Post URL: Providing an incorrect or malformed LinkedIn post URL may cause API errors.
  • Timeouts: Network issues or slow responses might trigger timeouts; adjust the timeout property if needed.
  • API Rate Limits: Excessive requests may lead to rate limiting; implement retry logic or reduce request frequency.
  • Incorrect Timestamp Format: The start time must be a valid Unix timestamp in milliseconds; otherwise, the API may reject it.

To resolve errors:

  • Verify API key and credential setup.
  • Confirm the LinkedIn post URL is correct and accessible.
  • Adjust timeout and retry count in advanced options.
  • Check network connectivity and proxy settings if applicable.

Links and References

Discussion