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 discussion-related content programmatically. Specifically, for the Discussion resource and the Remove Assignee operation, it removes a specified assignee from a discussion post identified by its content ID.
This functionality is useful in scenarios where task or responsibility assignments within discussions need to be updated dynamically, such as when a team member is no longer responsible for a particular discussion topic or issue.
Practical example:
- Automatically unassign a user from a discussion thread when their involvement ends.
- Manage workload distribution by removing assignees who have completed their tasks.
Properties
| Name | Meaning |
|---|---|
| Content ID | The unique identifier of the discussion content (post) from which the assignee will be removed. |
| Assignee | The identifier (e.g., username or user ID) of the assignee to remove from the discussion. |
Output
The node outputs a JSON object representing the response from the Discuss Kit API after removing the assignee. This typically includes confirmation of the removal or the updated state of the discussion post's assignees.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Discuss Kit API endpoint that manages posts and assignees.
- Needs an API authentication token or API key credential configured in n8n to authorize requests to the Discuss Kit service.
- Uses internal helper functions to make HTTP requests to the API.
Troubleshooting
Common issues:
- Invalid or missing Content ID: The API call will fail if the provided content ID does not exist or is malformed.
- Assignee not found: Attempting to remove an assignee who is not assigned to the content may result in an error.
- Authentication errors: Missing or invalid API credentials will prevent successful API calls.
Error messages and resolutions:
"404 Not Found": Verify that the Content ID corresponds to an existing discussion post."401 Unauthorized"or"403 Forbidden": Check that the API key or authentication token is correctly set up and has sufficient permissions."400 Bad Request": Ensure that both Content ID and Assignee fields are correctly filled and valid.
Links and References
- Discuss Kit API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding how API requests are made)