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
- Task Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to manage tasks and their reactions. Specifically, the "Remove a Reaction" operation under the "Task" resource allows users to remove a previously added reaction (such as an emoji or text) from either a task or a comment within Vikunja.
Common scenarios for this node include:
- Automating cleanup of reactions on tasks or comments based on workflow conditions.
- Managing user feedback or status indicators represented by reactions in task management.
- Synchronizing reaction states between Vikunja and other systems.
For example, if a team uses emoji reactions to indicate task priority or status, this node can programmatically remove outdated or incorrect reactions.
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 in length. |
Output
The node outputs JSON data representing the result of the remove reaction operation. This typically includes confirmation of the removal or details about the updated task or comment state after the reaction has been removed.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Vikunja instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL of the Vikunja API must be set correctly in the credentials.
Troubleshooting
- Invalid ID errors: Ensure that the Task or Comment ID provided exists and is correct.
- Reaction not found: If the specified reaction does not exist on the target entity, the operation may fail or have no effect.
- Authentication failures: Verify that the API key/token is valid and has sufficient permissions.
- API URL misconfiguration: Confirm the base URL does not have trailing slashes and points to the correct Vikunja server.
- Reaction value length: The reaction string should not exceed 20 characters; longer values might cause errors.