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 blog content, specifically supporting operations such as updating existing blog posts. It allows users to modify key attributes of a blog post like its title, content, associated board, labels, assignees, and slug. This is useful in scenarios where automated workflows need to keep blog content up-to-date, for example:
- Automatically updating blog posts based on external data changes.
- Managing blog metadata such as labels or assignees programmatically.
- Adjusting blog slugs or content formatting through automation.
Properties
| Name | Meaning |
|---|---|
| Title | The new title of the blog post to update. |
| Content | The updated content of the blog post, provided as a JSON string. |
| Board | The ID of the board to which this blog post belongs. |
| Labels | Comma-separated list of labels to assign to the blog post. |
| Assignees | Comma-separated list of decentralized IDs (DIDs) representing assignees for the blog post. |
| Content ID | The unique identifier of the blog post to update (required). |
| Slug | The URL-friendly slug for the blog post. |
Output
The node outputs an array of JSON objects representing the updated blog post returned from the Discuss Kit API after the update operation. The structure typically includes fields such as:
id: Unique identifier of the blog post.title: Updated title.content: Updated content.boardId: Associated board ID.labels: Array of labels assigned.assignees: Array of assignee DIDs.slug: Updated slug.- Other metadata fields as returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Discuss Kit API endpoint.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- Uses internal helper function to make HTTP requests to the Discuss Kit API.
Troubleshooting
Common issues:
- Invalid or missing Content ID will cause the update request to fail.
- Providing malformed JSON string in the Content property may result in API errors.
- Incorrect board ID or label names might lead to partial updates or errors.
- Network or authentication failures can prevent successful API calls.
Error messages and resolutions:
- "Content ID is required" — Ensure the Content ID property is set correctly.
- "Unauthorized" or "Authentication failed" — Verify that the API authentication token is valid and properly configured.
- "Invalid input data" — Check that all required fields are correctly formatted, especially the content JSON string.
- "Resource not found" — Confirm that the specified blog post ID exists in the system.