Actions27
- Standard Actions
- Sales Navigator Actions
- Other Actions
Overview
This node, named "Linked API," allows users to interact with LinkedIn accounts and retrieve real-time data related to their professional network. Specifically, the "Retrieve Connections" operation under the "Standard" resource fetches a list of LinkedIn connections based on various filter criteria. This is useful for automating workflows that require up-to-date information about your LinkedIn contacts, such as CRM updates, targeted marketing campaigns, or networking analysis.
Practical examples include:
- Automatically retrieving a limited number of connections filtered by job position or location.
- Extracting connections who attended specific schools or worked at certain companies.
- Integrating LinkedIn connection data into other systems via webhook callbacks.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | URL where the response will be sent via webhook after the operation completes. |
| Limit | Maximum number of connection results to return (minimum 1). |
| Additional Filter Fields | Optional filters to narrow down the connections retrieved: |
| - First Name | Filter connections by first name. |
| - Last Name | Filter connections by last name. |
| - Position | Filter connections by job position/title. |
| - Locations | Filter connections by locations; multiple values separated by semicolons (e.g., "New York; London"). |
| - Industries | Filter connections by industries; multiple values separated by semicolons (e.g., "Technology; Finance"). |
| - Current Companies | Filter connections by current companies; semicolon-separated list (e.g., "Google; Microsoft"). |
| - Previous Companies | Filter connections by previous companies; semicolon-separated list (e.g., "Apple; Facebook"). |
| - Schools | Filter connections by schools attended; semicolon-separated list (e.g., "Stanford University; MIT"). |
Output
The node outputs JSON data containing the retrieved LinkedIn connections matching the specified filters and limit. Each item in the output typically represents a connection with details such as name, position, company, location, and other relevant profile information.
If the node supports binary data output, it would generally relate to profile images or attachments, but this is not indicated in the provided code or properties.
Dependencies
- Requires an API key credential for authenticating with the Linked API service.
- The node sends requests to the base URL
https://api.linkedapi.io/automationusing POST method. - A valid webhook URL must be provided to receive asynchronous responses from the API.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Missing or invalid webhook URL can cause the operation to fail or not return results.
- Providing improperly formatted filter fields (e.g., missing semicolons between multiple values) may lead to unexpected filtering behavior.
- Exceeding the allowed limit or providing a limit less than 1 might result in errors or no data returned.
- Network or authentication failures due to incorrect API credentials.
Error messages:
- Errors related to authentication usually indicate invalid or missing API keys; verify credentials.
- Validation errors for input parameters suggest checking the format and presence of required fields like webhook URL and limit.
- Timeout or connectivity errors imply network issues or problems reaching the Linked API service endpoint.
Links and References
- LinkedIn API Documentation
- n8n Webhook Documentation
- Linked API Service (official site for the used API)