Discuss Kit icon

Discuss Kit

Consume Discuss Kit API

Overview

This node integrates with the Discuss Kit API to manage various content types such as discussions, blogs, bookmarks, documentation, comments, labels, boards, and search queries. Specifically for the Documentation resource with the Publish operation, it allows users to publish a draft documentation post by its ID.

Typical use cases include automating the publishing workflow of documentation content within a knowledge base or collaborative platform. For example, after creating or updating a documentation draft, this node can be used to programmatically publish it, making the content publicly available or visible to the intended audience.

Properties

Name Meaning
Content ID The unique identifier of the documentation content to be published. This is a required string input.

Output

The node outputs the JSON response returned from the Discuss Kit API after publishing the documentation content. This typically includes the full details of the published document, such as its ID, title, content, locale, slug, order, parent ID, and other metadata fields relevant to the documentation.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the Discuss Kit API endpoint.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests to the Discuss Kit service.
  • Uses internal helper functions to make HTTP requests to the API (blockletComponentApiRequest).

Troubleshooting

  • Common issues:

    • Invalid or missing Content ID: Ensure the "Content ID" property is correctly set and corresponds to an existing documentation draft.
    • Authentication errors: Verify that the API key or authentication token is properly configured and has sufficient permissions.
    • Network or API downtime: Check network connectivity and Discuss Kit API status.
  • Error messages:

    • "error": "Not Found": The specified Content ID does not exist or is incorrect.
    • "error": "Unauthorized": Authentication credentials are missing or invalid.
    • Timeout or connection errors: May indicate network issues or API unavailability.

To resolve these, double-check input parameters, credentials, and network conditions.

Links and References

Discussion