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 various content types such as discussions, blogs, bookmarks, and documentation. Specifically for the Documentation - Delete operation, it allows users to delete a documentation entry by its unique Content ID. This is useful in scenarios where outdated or incorrect documentation needs to be removed from the system.
Practical examples include:
- Automatically cleaning up deprecated documentation pages.
- Removing test or draft documents after publishing final versions.
- Managing content lifecycle by deleting obsolete docs programmatically.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the documentation content to delete. |
Output
The output JSON contains the response from the API after attempting to delete the specified documentation content. Typically, this will be an empty object or confirmation message indicating successful deletion. No binary data is returned.
Example output structure (conceptual):
{}
Dependencies
- Requires access to the Discuss Kit API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- Uses internal helper functions to make HTTP requests to the Discuss Kit backend.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Content ID will result in an error from the API.
- Missing or incorrect API authentication may cause authorization failures.
- Network connectivity problems can prevent the node from reaching the API.
Error messages and resolutions:
"404 Not Found": The Content ID does not exist. Verify the ID before retrying."401 Unauthorized"or"403 Forbidden": Check that the API key or token is correctly set up and has sufficient permissions.- Timeout errors: Ensure network stability and API endpoint availability.
Links and References
- Discuss Kit API Documentation (general reference for API endpoints)
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)