Actions66
- Board Actions
- Bookmark Actions
- Blog Actions
- Comment Actions
- Discussion Actions
- Documentation Actions
- Label Actions
- Search Actions
Overview
This node interacts with the Discuss Kit API to manage blog content, specifically allowing you to remove an assignee from a blog post. It is useful in scenarios where task or responsibility assignments on blog posts need to be updated dynamically, such as when a team member is no longer responsible for a particular blog entry.
For example, if a blog post was previously assigned to a user for review or editing and that assignment needs to be revoked, this node operation can remove that assignee efficiently.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the blog content (blog post) from which the assignee will be removed. |
| Assignee | The identifier (e.g., username or user ID) of the assignee to be removed from the blog post. |
Output
The output JSON contains the response from the Discuss Kit API after attempting to remove the assignee. Typically, this will be an object representing the updated state of the blog post or a confirmation of successful removal. The exact structure depends on the API's response but generally includes details about the blog post and its current assignees.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Discuss Kit API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- Uses internal helper functions to make HTTP requests to the API endpoints.
Troubleshooting
Common Issues:
- Invalid or missing Content ID or Assignee values will cause the API request to fail.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Attempting to remove an assignee who is not currently assigned may return an error or no change.
Error Messages:
"error": "Assignee not found"— The specified assignee does not exist on the blog post; verify the assignee identifier."error": "Unauthorized"— Check that the API key or token is correctly configured and has sufficient permissions."error": "Content not found"— The provided Content ID does not correspond to any existing blog post; confirm the ID.
To resolve these issues, ensure all input parameters are correct, the API credentials are valid, and the assignee is currently assigned to the blog post.
Links and References
- Discuss Kit API Documentation (general reference for API endpoints)
- n8n HTTP Request Node Documentation (for understanding how API calls are made within n8n)