Linkup API for LinkedIn icon

Linkup API for LinkedIn

Automate LinkedIn with Linkup

Actions36

Overview

The "Get Received Invitations" operation of the Linkup API node for LinkedIn allows users to retrieve a list of LinkedIn invitations they have received. This is useful for automating the management of incoming connection requests or organizational invitations on LinkedIn, enabling workflows that can analyze, filter, or respond to these invitations programmatically.

Practical examples include:

  • Automatically fetching all pending connection requests to review them in bulk.
  • Integrating with CRM systems to log received invitations.
  • Triggering notifications or follow-up actions based on new invitations.

Properties

Name Meaning
Invitation Type Type of invitation to filter by (e.g., CONNECTION, ORGANIZATION).
Number of Results Maximum number of invitations to retrieve.
Start Page The first page number to retrieve (for pagination).
End Page The last page number to retrieve (for pagination).
Country Code Country code used for proxy selection (e.g., FR for France, US for United States).
Timeout Request timeout duration in milliseconds.
Retry Count Number of retry attempts if the request fails.

These properties are grouped under "Linkup Parameters" and "Advanced Options" collections.

Output

The node outputs JSON data containing the response from the Linkup API for the received invitations request. The output includes:

  • The main data returned by the API representing the list of received invitations.
  • A _debug object containing:
    • requestBody: The exact request payload sent to the API.
    • requestHeaders: HTTP headers used in the request.
    • endpoint: The API endpoint URL called.
    • apiResponse: The raw response from the API.
  • A _meta object with metadata including:
    • resource: The resource name ("network").
    • operation: The operation name ("getReceivedInvitations").
    • timestamp: The timestamp when the request was made.
    • nodeVersion: The version of the node implementation.

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

The node does not output binary data.

Dependencies

  • Requires an API key credential for the Linkup API service.
  • Needs configuration of the Linkup API credentials within n8n, including the API key and optionally LinkedIn email, password, and country code.
  • Uses the Linkup API endpoint at https://api.linkupapi.com/v1/network/invitations.
  • Network connectivity to the Linkup API service is required.

Troubleshooting

  • Missing API Key: If the API key credential is not configured or invalid, the node will throw an error indicating the missing API key. Ensure the API key is correctly set up in the node credentials.
  • Timeouts: Requests may time out if the API is slow or network issues occur. Adjust the "Timeout" property or check network connectivity.
  • Invalid Parameters: Providing incorrect values for parameters like invitation type or country code may result in empty responses or errors. Verify parameter correctness.
  • API Rate Limits: Excessive requests might be throttled by the Linkup API. Implement retry logic or reduce request frequency using the "Retry Count" property.
  • Error Messages: Errors returned by the API will be included in the output's error field. Review the message for clues and consult Linkup API documentation if needed.

Links and References

Discussion