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
The node interacts with the Unipile API to list reactions associated with a specific user. It is designed to retrieve reaction data such as likes, emojis, or other forms of user engagement tied to a particular identifier within an account context. This node is useful in scenarios where you want to analyze user interactions, monitor engagement metrics, or aggregate reaction data for reporting or further processing.
For example, you might use this node to:
- Fetch all reactions made by a user identified by a unique ID within a given account.
- Paginate through large sets of reactions using cursor-based pagination.
- Limit the number of reactions retrieved per request to optimize performance.
Properties
| Name | Meaning |
|---|---|
| Identifier | The unique identifier of the user whose reactions are to be listed. |
| Account ID | The identifier of the account under which the user's reactions are queried. |
| Additional Fields | Optional parameters to refine the query: |
| - Cursor | A pagination cursor to fetch the next set of results. |
| - Limit | Maximum number of reaction results to return (minimum 1, default 50). |
Output
The node outputs JSON data containing the list of reactions corresponding to the specified user and account. The structure typically includes details about each reaction, such as type, timestamp, and any metadata provided by the Unipile API.
If the API supports pagination, the output may also include pagination cursors or tokens to fetch subsequent pages.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Unipile API via an API key credential.
- The base URL for API requests is configured from the credential's DSN property.
- Proper permissions on the Unipile account to access user reaction data.
Troubleshooting
- Missing or invalid Identifier/Account ID: Ensure both fields are provided and correctly correspond to existing entities in Unipile.
- API authentication errors: Verify that the API key credential is valid and has not expired.
- Pagination issues: If using the cursor field, ensure it is correctly obtained from previous responses; otherwise, no results may be returned.
- Limit value errors: The limit must be at least 1; setting it below this may cause errors.
Links and References
- Unipile API Documentation (hypothetical link)
- Pagination concepts: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#pagination