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. Specifically, the Get Conversation Messages operation under the Message resource retrieves the message history of a LinkedIn conversation. This is useful for workflows that need to analyze or process past LinkedIn messages within a specific conversation thread.

Typical use cases include:

  • Extracting conversation history for CRM enrichment.
  • Monitoring ongoing conversations for sentiment analysis or follow-up automation.
  • Archiving LinkedIn messages for compliance or record-keeping.

For example, you can retrieve the last 10 messages from a particular LinkedIn conversation by specifying its unique conversation ID.

Properties

Name Meaning
Conversation ID Unique LinkedIn conversation identifier
Number of Results Number of messages to retrieve (default: 10)
Start Page First page of results to retrieve (default: 1)
End Page Last page of results to retrieve (default: 1)
Country Code Country code for proxy selection (e.g., FR for France, US for United States)
Timeout Request timeout in milliseconds (default: 30000 ms)
Retry Count Number of retries on failure (default: 3)

These properties allow you to control which conversation's messages are fetched, how many messages to retrieve, pagination through pages of messages, and network/proxy settings based on country.

Output

The node outputs JSON data containing the retrieved conversation messages. The output structure includes:

  • _debug: Debug information including the request body sent, request headers, endpoint URL, and raw API response.
  • The main API response fields representing the conversation messages and related metadata.
  • _meta: Metadata about the resource (message), operation (getConversationMessages), timestamp of execution, and node version.

Example output snippet (simplified):

{
  "json": {
    "_debug": {
      "requestBody": { /* parameters sent */ },
      "requestHeaders": { /* HTTP headers */ },
      "endpoint": "/messages/conversation-messages",
      "apiResponse": { /* raw API response with messages */ }
    },
    "messages": [
      {
        "id": "12345",
        "sender": "https://www.linkedin.com/in/user1",
        "text": "Hello!",
        "timestamp": "2024-06-01T12:00:00Z"
      },
      ...
    ],
    "_meta": {
      "resource": "message",
      "operation": "getConversationMessages",
      "timestamp": "2024-06-01T12:30:00Z",
      "nodeVersion": "1.2.31"
    }
  },
  "pairedItem": {
    "item": 0
  }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an active Linkup API key credential configured in n8n.
  • The node makes HTTP POST requests to the Linkup API endpoint https://api.linkupapi.com/v1/messages/conversation-messages.
  • Proxy selection can be influenced by the country code parameter.
  • Optional timeout and retry count parameters control request behavior.

Troubleshooting

  • Missing API Key Error: If the API key credential is not set or invalid, the node will throw an error indicating the missing API key. Ensure your Linkup API key is correctly configured in n8n credentials.
  • Invalid Conversation ID: Providing an incorrect or non-existent conversation ID may result in empty results or API errors. Verify the conversation ID is correct.
  • Timeouts: If the request times out, consider increasing the Timeout property or checking network connectivity.
  • API Rate Limits: Excessive requests may trigger rate limiting; use the Retry Count property to handle transient failures gracefully.
  • Country Code Issues: Using an unsupported or incorrect country code might cause proxy selection problems. Use valid ISO country codes like FR, US, UK, etc.

Links and References

This summary covers the static analysis of the node’s execute method and relevant properties for the Message > Get Conversation Messages operation.

Discussion