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 comments associated with a specific user. It is designed to retrieve user comments by specifying an identifier and account ID, with optional pagination controls. This node is useful in scenarios where you want to aggregate or analyze user-generated comments from the Unipile platform, such as monitoring user feedback, tracking engagement, or integrating comment data into workflows.
Practical examples:
- Fetching recent comments made by a user for sentiment analysis.
- Displaying user comments in a dashboard or report.
- Automating responses or notifications based on new user comments.
Properties
| Name | Meaning |
|---|---|
| Identifier | The unique identifier of the user whose comments are to be listed. |
| Account ID | The account identifier under which the user exists; used to scope the request. |
| Cursor | (Optional) A cursor string used for paginating through large sets of comments. |
| Limit | (Optional) Maximum number of comment results to return; minimum value is 1, default 50. |
Output
The node outputs JSON data containing the list of comments retrieved from the Unipile API for the specified user. Each item in the output typically represents a single comment with its associated metadata (such as content, timestamp, author details, etc.). If pagination is used, the output may also include information about cursors or tokens for fetching subsequent pages.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured via credentials.
- Network connectivity to the Unipile API endpoint is necessary.
Troubleshooting
- Missing or invalid credentials: Ensure that a valid API authentication token is provided in the node's credentials configuration.
- Invalid identifiers: Verify that the
IdentifierandAccount IDvalues correspond to existing entities in the Unipile system. - Pagination issues: When using the
Cursorproperty, ensure the cursor value is correctly obtained from previous responses to avoid empty or repeated results. - API rate limits or errors: If the API returns errors related to rate limiting or server issues, consider implementing retry logic or checking service status.
Links and References
- Unipile API Documentation (example placeholder link)
- n8n documentation on HTTP Request Node for understanding API interactions