Linkup API for LinkedIn icon

Linkup API for LinkedIn

Automate LinkedIn with Linkup

Actions36

Overview

The "Get Message Inbox" operation of the Linkup API node retrieves a list of LinkedIn conversations (message inbox) for the authenticated user. This node is useful for automating the monitoring and management of LinkedIn messages, enabling workflows that can analyze incoming messages, trigger responses, or integrate LinkedIn messaging data with other systems.

Practical examples include:

  • Automatically fetching recent LinkedIn conversations to analyze message content or sender information.
  • Integrating LinkedIn inbox data into CRM or customer support tools.
  • Triggering alerts or follow-up actions based on new messages received.

Properties

Name Meaning
Invitation Type Invitation type filter such as CONNECTION, ORGANIZATION, etc. (optional)
Number of Results Number of conversation results to retrieve (default: 10)
Start Page First page number to retrieve (default: 1)
End Page Last page number to retrieve (default: 1)
Country Code Country code used for proxy selection (e.g., FR for France, US for United States) (default: FR)
Name Meaning
Timeout Request timeout in milliseconds (default: 30000)
Retry Count Number of retries on failure (default: 3)

These properties are grouped under two collections:

  • Linkup Parameters (networkListParams): controls pagination, filtering by invitation type, and country proxy.
  • Advanced Options (additionalFields): controls request timeout and retry behavior.

Output

The output JSON contains the response from the Linkup API's /messages/inbox endpoint. It includes:

  • The main data representing the list of LinkedIn conversations retrieved.
  • A _debug object containing:
    • requestBody: The exact request payload sent to the API.
    • requestHeaders: HTTP headers used in the request.
    • endpoint: The API endpoint called.
    • apiResponse: The raw response from the API.
  • A _meta object with metadata about the resource ("message"), operation ("getMessageInbox"), timestamp of execution, and node version.
  • pairedItem indicating the input item index this output corresponds to.

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for the Linkup API service.
  • The node makes HTTP POST requests to the Linkup API endpoint at https://api.linkupapi.com/v1/messages/inbox.
  • Proper configuration of the API key credential in n8n is necessary.
  • Optionally, country codes can be specified to select proxies for requests.

Troubleshooting

  • Missing API Key Error: If the API key credential is not configured or invalid, the node will throw an error indicating the missing API key. Ensure the Linkup API key is set up correctly in n8n credentials.
  • Timeouts or Network Errors: Requests may fail due to network issues or slow responses. Adjust the "Timeout" property or increase "Retry Count" to improve reliability.
  • Invalid Parameter Values: Providing incorrect country codes or invalid pagination numbers may result in API errors or empty results. Verify parameter values before running.
  • API Rate Limits: The Linkup API may enforce rate limits; if exceeded, errors will occur. Implement retry logic or reduce request frequency accordingly.

Links and References

Discussion