Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
The node integrates with the Discuss Kit API to manage various content types such as discussions, blogs, bookmarks, and documentation. Specifically, for the Documentation resource with the Update Settings operation, it updates settings like the cover image and slug of a documentation entry identified by its ID.
This node is useful in scenarios where you want to programmatically update metadata or settings of documentation content within a Discuss Kit-powered platform. For example, you might automate updating the cover image or URL slug of a document after processing or generating new content elsewhere.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the documentation content to update (required). |
| Slug | The URL-friendly string representing the document's address; used to update the slug. |
| Cover Image | The URL or path to the cover image to set for the documentation content. |
Output
- The output JSON contains the updated documentation object returned from the Discuss Kit API after applying the settings changes.
- This typically includes fields such as the document's ID, updated slug, cover image URL, and other metadata reflecting the current state after the update.
- 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 will cause the API request to fail.
- Incorrect or unauthorized API credentials will result in authentication errors.
- Providing invalid slug or cover image URLs may cause the API to reject the update.
Error messages:
"error": "Content not found"— Verify that the Content ID exists."error": "Unauthorized"— Check API credentials and permissions."error": "Invalid slug format"— Ensure the slug follows allowed patterns.
To resolve errors, confirm all required parameters are correctly set, and the API credentials have sufficient permissions.
Links and References
- Discuss Kit API Documentation (general reference for API endpoints)
- n8n HTTP Request Node Documentation (for understanding API request handling)