Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
This node integrates with the Discuss Kit API to manage discussion content and related entities such as blogs, bookmarks, documents, labels, boards, comments, and search queries. Specifically for the Discussion resource with the Add Label operation, it allows users to add a label to an existing discussion post by specifying the post's ID and the label name.
Common scenarios where this node is beneficial include:
- Automatically tagging discussion posts based on certain triggers or workflows.
- Organizing discussions by adding relevant labels for categorization.
- Enhancing content management systems by programmatically managing discussion metadata.
For example, after creating a new discussion post via another workflow step, you can use this node to add a label like "Important" or "Bug" to that post to facilitate filtering and prioritization.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the discussion post (or other content types) to which the label will be added. |
| Label | The label string to add to the specified content. |
Output
The node outputs the JSON response from the Discuss Kit API after performing the add label operation. This typically includes the updated state of the discussion post or confirmation of the label addition. The output is structured as an array of JSON objects, each corresponding to an input item processed.
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 internal helper functions to make HTTP requests to the Discuss Kit API.
Troubleshooting
Common issues:
- Invalid or missing Content ID: Ensure the provided ID corresponds to an existing discussion post.
- Label not found or invalid: Confirm the label string is valid and exists if required by the API.
- Authentication errors: Verify that the API key or token is correctly set up and has sufficient permissions.
- Network or API downtime: Check connectivity and Discuss Kit service status.
Error messages:
"error": "Not Found": The specified content ID does not exist."error": "Unauthorized": Authentication failed; check API credentials."error": "Bad Request": Input parameters are invalid or missing.
Resolving these usually involves verifying input parameters, ensuring correct credentials, and confirming API availability.
Links and References
- Discuss Kit Official Documentation
- Discuss Kit API Reference
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)