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, documents, comments, labels, boards, and search queries. Specifically for the Discussion - Delete operation, it deletes a discussion post identified by its unique Content ID.
Use cases include automating content management workflows where you need to programmatically remove discussion posts from your platform. For example, you might want to delete outdated or inappropriate discussions automatically based on certain triggers or conditions in your workflow.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the discussion post to delete. This is required to specify which discussion should be removed. |
Output
The output JSON contains the response from the Discuss Kit API after attempting to delete the specified discussion post. Typically, this will be an empty object or confirmation message indicating successful deletion. If the deletion fails, the output may contain error details.
No binary data is produced by this operation.
Dependencies
- Requires access to the Discuss Kit API.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- Uses internal helper functions to make HTTP requests to the Discuss Kit endpoints.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Content ID will result in an error from the API.
- Missing or incorrect API authentication credentials can cause authorization failures.
- Network connectivity problems may prevent the node from reaching the Discuss Kit API.
Error messages:
"error": "Not Found"— The specified Content ID does not exist; verify the ID."error": "Unauthorized"— Authentication failed; check your API key or token.- Timeout or network errors — Ensure your environment has internet access and the API endpoint is reachable.
To resolve these, double-check the Content ID, ensure valid API credentials are set up in n8n, and confirm network connectivity.
Links and References
- Discuss Kit API Documentation (generic placeholder link)
- n8n documentation on creating custom nodes