Actions57
- Label Actions
- Project Actions
- Add a Team
- Add a User
- Create
- Create a Kanban Bucket
- Create a Link Share
- Create a Project View
- Delete
- Delete a Kanban Bucket
- Delete a Link Share
- Delete a Project View
- Duplicate
- Get
- Get All Link Shares
- Get All Project Views
- Get All Teams
- Get All Users
- Remove a Team From a Project
- Remove a User From a Project
- Update
- Update a Kanban Bucket
- Update a Project View
- Update a Team's Rights on a Project
- Update a User's Rights on a Project
- Team Actions
- Task Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to manage reactions on tasks or comments within a task management system. Specifically, the "Remove a Reaction" operation under the "Task" resource allows users to remove an existing reaction (such as an emoji) from a specified task or comment.
Common scenarios include:
- Removing mistakenly added emoji reactions from tasks or comments.
- Managing and updating team feedback or status indicators on tasks by removing outdated or incorrect reactions.
Practical example:
- A user wants to remove a thumbs-up emoji reaction from a specific task after the issue has been resolved or the reaction is no longer relevant.
Properties
| Name | Meaning |
|---|---|
| Task or Comment ID | The numeric ID of the task or comment from which you want to remove the reaction. |
| Reaction Kind | Specifies whether the reaction is on a "Task" or a "Comment". |
| Reaction | The actual reaction value to remove, typically an emoji or any UTF character/text up to 20 characters. |
Output
The node outputs JSON data representing the result of the remove reaction operation. This typically includes confirmation that the reaction was successfully removed or details about the updated task/comment state. There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node sends HTTP requests with JSON content type headers.
Troubleshooting
- Invalid ID error: If the provided Task or Comment ID does not exist, the API will likely return an error. Verify the ID is correct.
- Reaction not found: Attempting to remove a reaction that does not exist on the specified entity may cause an error or no change. Confirm the reaction value matches exactly.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- API URL misconfiguration: The base URL should not have trailing slashes; otherwise, requests might fail.