Discuss Kit icon

Discuss Kit

Consume Discuss Kit API
Join our community

Actions66

Overview

This node integrates with the Discuss Kit API to manage various content types such as discussions, blogs, bookmarks, comments, documentation, labels, boards, and search queries. Specifically for the Documentation resource with the Create operation, it allows users to create new documentation entries within a board or hierarchy.

Typical use cases include:

  • Automating the creation of structured documentation pages in a collaborative environment.
  • Organizing documents with parent-child relationships and display order.
  • Assigning labels and assignees to documentation for better categorization and responsibility tracking.
  • Setting language and slug for SEO-friendly URLs and localization.

For example, a user can create a new documentation page titled "API Reference" under a specific board, assign relevant team members, set its display order, and specify its parent document to build a nested documentation structure.

Properties

Name Meaning
Title Title of the documentation (required).
Content Content of the documentation as a JSON string (required).
Board ID of the board to which this documentation belongs.
Labels Comma-separated labels for categorizing the documentation.
Assignees Comma-separated decentralized identifiers (DIDs) of assignees responsible for the documentation.
Language Language code of the content (default is "en").
Slug URL-friendly slug for the documentation page.
Parent ID ID of the parent documentation item to establish hierarchy.
Display Order Numeric value indicating the display order of the documentation (default is -1).

Output

The node outputs the created documentation object as JSON. This includes all properties returned by the Discuss Kit API after creation and update calls, such as the assigned ID, title, content, labels, assignees, locale, slug, parentId, order, and other metadata.

No binary data output is involved in this operation.

Dependencies

  • Requires access to the Discuss Kit API endpoint.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node uses internal helper functions to make HTTP requests to the Discuss Kit API.

Troubleshooting

  • Missing required fields: Ensure that both "Title" and "Content" are provided; otherwise, the API will reject the request.
  • Invalid Board ID or Parent ID: Providing incorrect IDs may cause errors or unexpected behavior. Verify these IDs exist in your Discuss Kit instance.
  • Authentication errors: If the API key or token is missing or invalid, requests will fail with authorization errors.
  • Malformed JSON content: The "Content" field expects a valid JSON string. Invalid JSON will cause the API to reject the request.
  • Slug conflicts: Using duplicate slugs might cause conflicts or overwrite issues depending on the backend configuration.

Links and References

Discussion