Actions85
- Account Actions
- Calendar Actions
- Email Actions
- LinkedIn Actions
- Close Job Posting
- Create Job Posting
- Download Applicant Resume
- Edit Job Posting
- Endorse Skill
- Get Company Profile
- Get Hiring Project by ID
- Get Hiring Projects
- Get Inmail Balance
- Get Job Applicant
- Get Job Applicants
- Get Job Offer
- Get Job Postings
- Get Raw Data
- Perform Action on Member
- Publish Job Posting
- Search
- Search Parameters
- Solve Job Publishing Checkpoint
- Messaging Actions
- Post Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Unipile API to list reactions on a specific post. It is useful for scenarios where you want to retrieve user engagement data such as likes, emojis, or other reaction types associated with a post in a social media or messaging context. For example, marketers or community managers can use this node to analyze audience interaction on posts by fetching all reactions and filtering them by account or comment.
Properties
| Name | Meaning |
|---|---|
| Post ID | The unique identifier of the post for which to list reactions. |
| Additional Fields | Optional parameters to refine the query: |
| - Account ID | Filter reactions from a specific account by its ID. |
| - Comment ID | Filter reactions related to a specific comment on the post. |
| - Cursor | A pagination cursor to fetch subsequent pages of results. |
| - Limit | Maximum number of reaction results to return (minimum 1, default 50). |
Output
The node outputs a JSON array containing the reactions retrieved from the Unipile API for the specified post. Each item in the array represents a single reaction, typically including details such as the reacting account, reaction type, timestamp, and possibly linked comment information if filtered by comment ID.
If the API supports it, the output may also include pagination metadata to facilitate fetching additional pages using the cursor.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Unipile API.
- An API authentication token or key credential must be configured in n8n to authorize requests.
- The base URL for the API is dynamically set from the credential's DSN property.
Troubleshooting
- Missing or invalid Post ID: The node requires a valid Post ID; ensure this field is correctly filled.
- API authentication errors: Verify that the API key or token is correctly configured and has sufficient permissions.
- Pagination issues: If using the cursor for pagination, ensure the cursor value is valid and corresponds to the previous response.
- Rate limiting or network errors: Handle possible API rate limits or connectivity problems by implementing retries or error handling workflows.
Links and References
- Unipile API Documentation (example placeholder link)
- n8n documentation on HTTP Request Node for understanding API integrations