Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
The node integrates with the Discuss Kit API to manage various content types such as discussions, blogs, bookmarks, documentation, comments, boards, labels, and search queries. Specifically for the Documentation resource with the Get Many operation, it retrieves multiple documentation entries from the Discuss Kit platform.
This node is useful when you want to programmatically fetch a list of documentation pages or articles from your Discuss Kit instance, for example, to display them in another system, synchronize content, or perform bulk processing.
Practical examples:
- Fetching all documentation pages to generate an external sitemap.
- Retrieving a limited number of recent docs for display on a dashboard.
- Integrating documentation content into a knowledge base or CMS.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all documentation entries or only up to a specified limit. |
| Limit | Maximum number of documentation entries to return (used if "Return All" is false). |
Note: The property Board is not applicable for the Documentation resource's Get Many operation based on the provided input properties.
Output
The output is a JSON array where each item represents a documentation entry retrieved from the Discuss Kit API. Each item contains fields describing the documentation content, such as its ID, title, content, locale, slug, order, parent-child relationships, labels, assignees, and other metadata depending on the Discuss Kit API response.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Discuss Kit API endpoint.
- Optionally uses an API key credential or similar authentication configured in n8n to authorize requests.
- The node relies on internal helper functions to make HTTP requests to the Discuss Kit API.
Troubleshooting
- Empty results: Ensure that the Discuss Kit instance has documentation entries available and that any filters (like boardId) are correctly set.
- Authentication errors: Verify that the API credentials are correctly configured and have sufficient permissions.
- Rate limiting or timeouts: Large result sets may cause delays; use the "Limit" property or enable "Return All" carefully.
- Unexpected response structure: Confirm that the Discuss Kit API version matches what the node expects.