Actions31
- Option Set Actions
- Public Query Actions
- Record Actions
- Role Actions
- Workflow Actions
- Worksheet Actions
Record → Get Discussions
AI-generatedOverview
This node operation retrieves discussions (comments and system messages) related to a specific record in a worksheet within the Hyper Application Platform (HAP). It is useful for scenarios where you want to fetch conversation threads, feedback, or audit trail messages associated with a particular data record. For example, a user might use this node to display all comments on a customer support ticket or to review system-generated logs attached to a sales order.
Properties
| Name | Meaning |
|---|---|
| Worksheet ID | The unique identifier of the worksheet containing the record. |
| Record ID | The unique row ID of the record whose discussions are being retrieved. |
| Page Size | Number of discussion entries to return per page (pagination size). |
| Page Index | The page number to retrieve, starting from 1 (for pagination). |
| Sort Type | The order in which discussions are sorted: "Latest First" or "Oldest First". |
| Discussion Type | Filter by type of discussions: "All", "Comments" only, or "System Messages" only. |
| Search | A search term to filter discussions by content. |
| Only With Attachments | Whether to return only discussions that include attachments (true/false). |
Output
The output contains a JSON array of discussion objects related to the specified record. Each discussion object typically includes details such as the message content, author, timestamp, type (comment or system message), and any attachments if present.
If attachments exist, they may be included as metadata or binary data references depending on the platform's API response structure.
Dependencies
- Requires an active connection to the Hyper Application Platform API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on the HAP API endpoints for fetching record discussions.
Troubleshooting
- Invalid Worksheet or Record ID: If the provided IDs do not exist or are incorrect, the node will likely return an error or empty results. Verify the IDs before running.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up.
- Pagination Issues: Requesting a page index beyond available pages may return empty results. Adjust page size and index accordingly.
- Empty Results: If no discussions match the filters (e.g., discussion type or search term), the output will be empty. Try broadening filters.
- Attachment Filtering: Setting "Only With Attachments" to true when no discussions have attachments will result in no data returned.