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 related entities. Specifically, the "Add a Reaction" operation on the "Task" resource allows users to add a reaction (such as an emoji or text) to either a task or a comment within Vikunja. This is useful for quickly expressing feedback or sentiment on tasks or comments without adding a full textual response.
Common scenarios include:
- Adding emoji reactions to tasks to indicate priority or status informally.
- Reacting to comments to acknowledge or respond non-verbally.
- Enhancing collaboration by allowing team members to express quick feedback.
Example: A user can add a thumbs-up emoji reaction to a task to show approval or agreement.
Properties
| Name | Meaning |
|---|---|
| Task or Comment ID | The numeric ID of the task or comment you want to react on. |
| Reaction Kind | The type of entity to react on; options are: Task or Comment. |
| Reaction | The actual reaction value, 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 reaction addition. This typically includes confirmation details such as the reaction added, the target entity ID, and possibly metadata about the updated task or comment.
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 for the Vikunja API must be set correctly in the credentials.
Troubleshooting
- Invalid ID errors: Ensure the Task or Comment ID provided exists and is correct.
- Authentication failures: Verify that the API key/token credential is valid and has sufficient permissions.
- Reaction value too long: The reaction string must not exceed 20 characters; otherwise, the API may reject it.
- Network issues: Confirm that the Vikunja server URL is reachable from the n8n environment.
Links and References
- Vikunja API Documentation – Official API docs for understanding endpoints and payloads.
- Vikunja GitHub Repository – Source code and issue tracker for Vikunja.