Actions8
- User Actions
- Chat Actions
- Post Actions
Overview
This node, named "HDW LinkedIn Management," allows users to manage LinkedIn accounts through the Horizon Data Wave API. Specifically, for the User resource and Get Connections operation, it retrieves a list of LinkedIn user connections. This is useful for scenarios where you want to analyze or process your LinkedIn network data, such as exporting connection lists, filtering connections by when they were made, or integrating connection data into other workflows.
Practical examples include:
- Fetching all connections made after a certain date to identify recent contacts.
- Limiting the number of connections retrieved to avoid large data loads.
- Using connection data to trigger follow-up actions like sending messages or invitations.
Properties
| Name | Meaning |
|---|---|
| Connected After | Filter users that were connected after this timestamp (Unix epoch time in seconds). |
| Count | Maximum number of connections to return (integer). |
| Timeout | Timeout in seconds for the API request. |
Output
The output is an array of JSON objects, each representing a LinkedIn connection returned by the API. Each item contains the connection's details as provided by the Horizon Data Wave API. The exact structure depends on the API response but typically includes user identifiers, names, connection timestamps, and possibly profile metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for the Horizon Data Wave LinkedIn API.
- The node uses the Horizon Data Wave API endpoint
https://api.horizondatawave.ai. - Proper configuration of the API credentials with an account ID is mandatory.
- Network connectivity to the Horizon Data Wave API service is required.
Troubleshooting
No credentials provided!
Error thrown if the API key credential is missing. Ensure the credential is configured in n8n.Account ID is missing in credentials!
The API key credential must include an account ID; verify the credential setup.API errors with HTTP status codes
The node surfaces detailed error information from the API response headers and body. Common issues might be rate limiting, invalid parameters, or authentication failures. Check the error message, HTTP status, and any API error details included in the output.Timeouts
If requests take longer than the specified timeout, consider increasing the timeout property or checking network conditions.Empty or incomplete results
Verify that theConnected Aftertimestamp is correctly formatted and that theCountis set appropriately.
Links and References
- Horizon Data Wave API Documentation (assumed public API docs)
- LinkedIn Developer Documentation (for general LinkedIn concepts)
If you need details on other resources or operations, feel free to ask!
