Discuss Kit icon

Discuss Kit

Consume Discuss Kit API
Join our community

Actions66

Overview

This node integrates with the Discuss Kit API to manage discussion content and related resources such as blogs, documents, bookmarks, boards, labels, comments, and search queries. Specifically, for the Discussion resource with the Update Content operation, it updates existing discussion posts by modifying properties like title, content, board association, labels, and assignees.

Typical use cases include:

  • Updating the text or metadata of a discussion post in a community forum or collaboration platform.
  • Changing the board/category where a discussion is posted.
  • Adding or removing labels or assignees to organize or assign responsibility for discussions.
  • Automating content management workflows that involve editing discussions programmatically.

Example: Automatically update the content and labels of a discussion post when certain conditions are met, such as after moderation or review.

Properties

Name Meaning
Title The new title of the discussion post.
Content The updated content of the discussion, provided as a JSON string representing the post body.
Board ID of the board (category) to which this discussion belongs.
Labels Comma-separated list of labels/tags to associate with the discussion.
Assignees Comma-separated list of decentralized identifiers (DIDs) representing users assigned to the discussion.
Content ID The unique identifier of the discussion post to update (required).
Slug A URL-friendly slug for the discussion content (optional, used in some operations).

Output

The node outputs the updated discussion post data as JSON. This typically includes all fields returned by the Discuss Kit API for a discussion post after the update, such as:

  • id: Unique identifier of the discussion.
  • title: Updated title.
  • content: Updated content.
  • boardId: Associated board ID.
  • labels: Array of labels.
  • assignees: Array of assigned user DIDs.
  • Other metadata fields as returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires access to the Discuss Kit API endpoint.
  • Needs an API authentication token or credential configured in n8n to authorize requests.
  • Uses internal helper functions to make HTTP requests to the Discuss Kit API.
  • No additional external services beyond Discuss Kit are required.

Troubleshooting

  • Common issues:

    • Invalid or missing Content ID will cause the update to fail.
    • Providing malformed JSON string in the Content property may result in API errors.
    • Insufficient permissions or invalid API credentials can lead to authorization errors.
    • Incorrect board ID or label names might cause the API to reject the update.

  • Error messages:

    • "error": "Content not found" — Verify the Content ID is correct.
    • "error": "Unauthorized" — Check API credentials and permissions.
    • "error": "Invalid input" — Ensure all required fields are correctly formatted, especially JSON content.

  • Resolution tips:

    • Double-check all required parameters before execution.
    • Validate JSON strings for the content field.
    • Confirm API credentials are properly set up in n8n.
    • Use the API documentation to verify valid values for board IDs, labels, and assignees.

Links and References

Discussion