Discuss Kit icon

Discuss Kit

Consume Discuss Kit API

Overview

This node integrates with the Discuss Kit API to manage comments related to various objects such as discussions, blogs, documents, bookmarks, and more. Specifically, the "Comment" resource with the "Get Many" operation allows users to retrieve multiple comments associated with a particular object ID.

Typical use cases include:

  • Fetching all comments for a specific discussion post or blog article.
  • Retrieving recent comments on a document or bookmark.
  • Aggregating user feedback or conversation threads linked to an object in your application.

For example, you might use this node to pull all comments from a discussion thread identified by its object ID to display them in a custom dashboard or to analyze user engagement.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit. Boolean: true returns all results.
Limit Maximum number of comment results to return when "Return All" is false. Number, minimum 1.
Object ID The unique identifier of the object (e.g., discussion post, blog, document) whose comments are fetched. Required string.

Output

The output is a JSON array where each item represents a comment object retrieved from the Discuss Kit API. Each comment includes details such as content, author, timestamps, replies, ratings, and other metadata embedded by the API.

If binary data were involved (not in this operation), it would typically represent attachments or media related to comments, but this operation focuses solely on JSON comment data.

Dependencies

  • Requires access to the Discuss Kit API endpoint.
  • Optionally uses an API authentication token or key configured in n8n credentials to authorize requests.
  • Utilizes internal helper functions to make HTTP requests to the Discuss Kit API.

Troubleshooting

  • Empty Results: If no comments are returned, verify that the provided Object ID is correct and that comments exist for that object.
  • API Errors: Common errors may include authentication failures or rate limits. Ensure your API credentials are valid and have sufficient permissions.
  • Limit Ignored: If "Return All" is set to true, the "Limit" property is ignored; ensure you configure these properties correctly based on your needs.
  • Timeouts: Large result sets may cause timeouts; consider using pagination or limiting results.

Links and References

Discussion