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 blog content settings. Specifically, the "Update Settings" operation for the "Blog" resource allows users to update metadata such as the cover image and slug of a blog post. This is useful when you want to modify the visual presentation or URL-friendly identifier of an existing blog entry without changing its main content.
Practical examples include:
- Updating the cover image of a blog post to reflect new branding or seasonal themes.
- Changing the slug (URL path segment) of a blog post to improve SEO or correct typos.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the blog content whose settings you want to update. |
| Slug | The URL-friendly string that identifies the blog post; used to change the blog's slug. |
| Cover Image | The URL or identifier of the cover image to set for the blog post. |
Output
The node outputs JSON data representing the updated blog content after applying the settings changes. This typically includes fields such as the blog's ID, title, content, slug, cover image URL, and other metadata returned by the Discuss Kit API.
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.
- Providing an invalid slug format may result in an error from the API.
- Network or authentication errors if the API key/credential is not properly configured.
Error messages:
"error": "Content not found"— Verify the Content ID is correct and exists."error": "Invalid slug format"— Ensure the slug contains only allowed characters.- Authentication errors — Check that the API key credential is valid and has necessary permissions.
Resolving these usually involves verifying input parameters and ensuring proper API credentials are set up in n8n.
Links and References
- Discuss Kit API Documentation
- n8n HTTP Request Node Documentation (for understanding API calls)