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
The node integrates with the Vikunja API to manage tasks and their reactions. 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 collaborative task management scenarios where team members want to quickly express feedback or acknowledgment without adding full comments.
Practical examples include:
- Adding a thumbs-up emoji reaction to a task to indicate approval.
- Reacting with a smiley face to a comment to show agreement or appreciation.
Properties
| Name | Meaning |
|---|---|
| Task or Comment ID | The numeric ID of the task or comment you want to react on. |
| Reaction Kind | Specifies whether the reaction is added to a "Task" or a "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 request. This typically includes confirmation details from the Vikunja API about the newly added reaction. The output does not handle binary data.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node sends requests to the Vikunja REST API endpoints related to tasks and comments.
Troubleshooting
- Invalid ID errors: Ensure that the Task or Comment ID provided exists and is correct.
- Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
- Reaction value too long: The reaction string must be no longer than 20 characters; exceeding this may cause errors.
- Network issues: Confirm that the Vikunja API URL is reachable from the n8n environment.
Links and References
- Vikunja API Documentation - Official API docs for understanding available endpoints and payloads.
- Vikunja GitHub Repository - Source code and issue tracker for Vikunja.