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 Discussion - Get operation, it retrieves detailed information about a single discussion post by its unique content ID.

Typical use cases include:

  • Fetching a specific discussion post to display or process its content in workflows.
  • Integrating discussion data into other systems or automations.
  • Monitoring or auditing discussion posts by retrieving their current state.

Example: You have a workflow that triggers when a new comment is added, and you want to fetch the full discussion details related to that comment for further processing or notifications.

Properties

Name Meaning
Content ID The unique identifier of the discussion post to retrieve. This is required to specify which discussion to get.

Output

The node outputs a JSON object representing the discussion post retrieved from the API. The structure typically includes fields such as:

  • id: Unique identifier of the discussion.
  • title: Title of the discussion.
  • content: Main content/body of the discussion.
  • boardId: Identifier of the board the discussion belongs to.
  • labels: Array of labels/tags associated with the discussion.
  • assignees: Array of users assigned to the discussion.
  • Other metadata fields like creation date, update date, locale, slug, etc.

The output is returned as an array of JSON objects (usually one item per execution since this is a "get by id" operation).

No binary data output is involved in this operation.

Dependencies

  • Requires access to the Discuss Kit API endpoint.
  • Optionally uses an API authentication token or key configured in n8n credentials (referred generically as an API key credential).
  • The node depends on internal helper functions to make HTTP requests to the Discuss Kit API.

Troubleshooting

  • Common issues:

    • Invalid or missing Content ID will cause the API request to fail.
    • Network connectivity problems or incorrect API credentials can result in authentication errors.
    • If the specified discussion ID does not exist, the API may return a 404 error.
  • Error messages:

    • "error": "Not Found" — The discussion with the given ID does not exist. Verify the Content ID.
    • "error": "Unauthorized" — Check that the API key credential is correctly set up and has proper permissions.
    • Timeout or network errors — Ensure the API endpoint is reachable and your network allows outbound requests.
  • Resolution tips:

    • Double-check the Content ID input for correctness.
    • Confirm API credentials are valid and properly configured in n8n.
    • Test connectivity to the Discuss Kit API outside n8n to isolate network issues.

Links and References

Discussion