Discuss Kit icon

Discuss Kit

Consume Discuss Kit API
Join our community

Actions66

Overview

The node integrates with the Discuss Kit API to manage discussion content settings. Specifically, for the Discussion resource and Update Settings operation, it updates metadata such as the cover image and slug of a discussion post identified by its content ID.

This node is useful when you want to programmatically modify the appearance or URL-friendly identifier (slug) of a discussion post in your community or forum platform powered by Discuss Kit. For example, you might update the cover image to reflect new branding or change the slug to improve SEO or readability.

Properties

Name Meaning
Content ID The unique identifier of the discussion post whose settings you want to update.
Slug The URL-friendly string representing the discussion post, used for linking or SEO.
Cover Image The URL or path to an image that will be used as the cover image for the discussion post.

Output

  • The output JSON contains the updated discussion post object returned from the Discuss Kit API after applying the settings changes.
  • This typically includes fields like id, cover, slug, and other metadata reflecting the current state of the discussion post.
  • No binary data output is produced by this operation.

Dependencies

  • Requires access to the Discuss Kit API endpoint.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • Uses the internal helper function to make HTTP PUT requests to /api/posts/{id}/settings endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing Content ID: The API call will fail if the provided ID does not correspond to an existing discussion post.
    • Incorrect or malformed slug: The slug must follow URL-safe formatting rules; otherwise, the API may reject it.
    • Unauthorized errors: Ensure the API key or token has sufficient permissions to update discussion posts.
    • Network or timeout errors when connecting to the Discuss Kit API.

  • Error messages:

    • "404 Not Found": The specified Content ID does not exist.
    • "401 Unauthorized" or "403 Forbidden": Authentication failed or insufficient permissions.
    • "400 Bad Request": Invalid input parameters, e.g., invalid slug format.

  • Resolutions:

    • Verify the Content ID is correct and exists.
    • Check the slug value for invalid characters.
    • Confirm API credentials are correctly set up and have required scopes.
    • Retry on transient network failures.

Links and References

Discussion