Discuss Kit icon

Discuss Kit

Consume Discuss Kit API
Join our community

Actions66

Overview

The node integrates with the Discuss Kit API to manage various content types such as discussions, blogs, bookmarks, documents, comments, labels, boards, and search queries. Specifically for the Bookmark resource with the Unpin operation, it allows users to remove the pinned status from a bookmark or related content by its content ID.

This node is useful in scenarios where you want to programmatically manage bookmarks within a discussion or content platform, such as unpinning outdated or irrelevant bookmarks to keep the content organized and up-to-date.

Practical examples:

  • Automatically unpin bookmarks after a certain date or event.
  • Manage bookmark pins based on user actions or workflow automation.
  • Clean up pinned items in bulk via automation.

Properties

Name Meaning
Content ID The unique identifier of the content (bookmark) to unpin. This is required to specify which bookmark should be unpinned.

Output

The output of the node is a JSON array containing the response from the Discuss Kit API after attempting to unpin the specified bookmark. The structure typically reflects the updated state of the bookmark or confirmation of the unpin action.

No binary data output is indicated in the source code.

Dependencies

  • Requires access to the Discuss Kit API.
  • Optionally uses an API key credential for authentication (configured in n8n credentials).
  • The node depends on internal helper functions to make HTTP requests to the Discuss Kit API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Content ID will cause the API request to fail.
    • Authentication errors if the API key or credentials are not properly configured.
    • Network or timeout errors when connecting to the Discuss Kit API.

  • Error messages:

    • Errors returned from the API will be included in the node output if "Continue On Fail" is enabled.
    • Typical error messages might include "Content not found", "Unauthorized", or "Invalid request".

  • Resolutions:

    • Ensure the Content ID is correct and exists in the system.
    • Verify that the API credentials are set up correctly in n8n.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion