Actions36
- Authentication Actions
- Profile Actions
- Company Actions
- Network Actions
- Message Actions
- Post Actions
- Recruiter Actions
- Data Actions
Overview
This node integrates with the Linkup API to automate LinkedIn activities related to posts. Specifically, the Get Post Reactions operation retrieves reactions on a specified LinkedIn post. This is useful for social media managers, marketers, or recruiters who want to analyze engagement on LinkedIn content automatically.
Typical use cases include:
- Monitoring how many and which types of reactions a LinkedIn post has received.
- Gathering data for reports on post performance.
- Triggering workflows based on reaction counts or types.
For example, you could use this node to fetch the latest reactions on a company announcement post and then send a summary report via email or update a CRM system.
Properties
| Name | Meaning |
|---|---|
| LinkedIn Post URL | The URL of the LinkedIn post to retrieve reactions from (e.g., https://www.linkedin.com/feed/update/xxx). |
| Reaction Type | Type of reaction to apply (only relevant for other operations like reacting). Options: 👍 Like, 🎉 Celebrate, 💪 Support, ❤️ Love, 💡 Insightful, 🤔 Curious. For Get Post Reactions, this is not used. |
| Message/Text | Comment text (not used in Get Post Reactions). |
| Duration (seconds) | Time spent on post in seconds (not used in Get Post Reactions). |
| Start Time (timestamp) | Unix timestamp in milliseconds marking when viewing started (not used in Get Post Reactions). |
| Number of Results | Number of reaction results to retrieve (default 10). |
| Start Page | First page of results to retrieve (default 1). |
| End Page | Last page of results to retrieve (default 1). |
| Country Code | Country code for proxy selection (e.g., FR, US, UK). Defaults to "FR". |
| Timeout | Request timeout in milliseconds (default 30000). |
| Retry Count | Number of retries on failure (default 3). |
Output
The node outputs JSON data containing the reactions retrieved from the LinkedIn post. The output includes:
_debug: Debug information including the request body sent, headers, endpoint URL, and raw API response.- The actual API response fields representing the post reactions.
_meta: Metadata about the resource (post), operation (getPostReactions), timestamp of execution, and node version.pairedItem: Information linking the output to the input item index.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for the Linkup API to authenticate requests.
- The node makes HTTP POST requests to the Linkup API endpoint
/posts/reactions. - The user must configure the API key credential in n8n before using this node.
- Optionally uses country codes 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.
- Invalid Post URL: Providing an incorrect or malformed LinkedIn post URL may result in API errors or empty responses. Verify the URL format.
- Timeouts: Network issues or slow API responses may cause timeouts. Adjust the Timeout property if needed.
- API Rate Limits: Excessive requests might be throttled by the Linkup API. Use the Retry Count property to handle transient failures gracefully.
- Country Code Proxy Issues: Using unsupported or incorrect country codes for proxy selection may lead to connection problems.
Links and References
- Linkup API Documentation — Official site to create an account and get API keys.
- LinkedIn Post URL format:
https://www.linkedin.com/feed/update/urn:li:activity:<activity_id>/
This summary covers the static analysis of the node's execute method and its configuration for the "Post" resource and "Get Post Reactions" operation.