Actions18
- Company Actions
- Search Actions
- Google Actions
- Group Actions
- User Actions
- Email Actions
- Post Actions
Overview
This node integrates with the Horizon Data Wave LinkedIn API to retrieve various types of LinkedIn data. Specifically, for the User resource and Get Reactions operation, it fetches reactions made by a LinkedIn user identified by their User URN. This is useful when you want to analyze or monitor the engagement a user has on LinkedIn posts, such as tracking who reacted to their content or understanding the user's interaction patterns.
Common scenarios:
- Marketing teams analyzing user engagement on LinkedIn.
- Recruiters or sales professionals monitoring interactions of potential leads.
- Social media analysts gathering reaction data for sentiment or influence analysis.
Example use case:
You provide the User URN of a LinkedIn profile, specify how many reactions you want to retrieve (e.g., 10), and optionally set a timeout. The node then returns the list of reactions associated with that user.
Properties
| Name | Meaning |
|---|---|
| User URN | The unique identifier of the LinkedIn user whose reactions you want to retrieve. Must include prefix, e.g., fsd_profile:ACoAA.... |
| Count | Maximum number of reaction results to return. Default is 10. |
| Timeout | Timeout in seconds for the API request. Default is 300 seconds. |
Output
The node outputs an array of JSON objects representing the reactions retrieved from the LinkedIn API for the specified user. Each item in the output corresponds to one reaction entry, containing details about the reaction such as type, reacting user, timestamp, and possibly related post information.
If multiple input items are processed, the output will be a concatenated list of all reactions fetched per input.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Horizon Data Wave LinkedIn API.
- Requires configuration of an API authentication credential (an API key or token) within n8n to authorize requests to the external service.
- The base URL used for API calls is
https://api.horizondatawave.ai.
Troubleshooting
- Timeouts: If the API call times out, consider increasing the "Timeout" property value.
- Invalid URN: Ensure the User URN includes the correct prefix and is valid; otherwise, the API may return errors or empty results.
- API Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate Limits: Excessive requests might trigger rate limiting by the API; implement delays or reduce request frequency if needed.
- Error Messages: On failure, the node returns error messages with details from the API response. Check these messages to identify issues like invalid parameters or network problems.
Links and References
- Horizon Data Wave LinkedIn API Documentation (hypothetical link based on base URL)
- LinkedIn Developer Documentation
- n8n HTTP Request Node documentation for configuring API credentials and handling responses.
