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
The node integrates with the Vikunja API to manage tasks and related entities. Specifically, for the Task - Add a Comment operation, it allows users to add a textual comment to an existing task identified by its Task ID. This is useful in scenarios where team members want to provide updates, feedback, or additional information directly on a task within their project management workflow.
Practical examples include:
- Adding progress notes or clarifications to a task.
- Logging communication or decisions made regarding a task.
- Collaborating asynchronously by leaving comments visible to all task participants.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to which the comment will be added. |
| Comment Text | The content of the comment to add. This is a multiline string representing the comment. |
Output
The node outputs JSON data representing the newly created comment object as returned by the Vikunja API. This typically includes details such as the comment's ID, text, author, creation timestamp, and associated task ID.
If the node supports binary data output (not indicated here), it would represent any file attachments or media related to the comment, but this operation focuses solely on textual comments.
Dependencies
- Requires an active connection to the Vikunja API via an API URL and an API authentication token configured in the node credentials.
- The base URL for API requests is derived from the provided API URL credential, ensuring no trailing slash.
- The node sends JSON-formatted requests and expects JSON responses.
Troubleshooting
- Missing or invalid Task ID: The operation requires a valid numeric Task ID. Ensure the Task ID exists in Vikunja and is correctly provided.
- Empty Comment Text: The comment text must not be empty; otherwise, the API may reject the request.
- Authentication errors: Verify that the API key/token credential is correctly set up and has sufficient permissions to add comments.
- Network issues: Check connectivity to the Vikunja server and ensure the API URL is correct.
- API errors: If the API returns errors, inspect the error message for details such as rate limits, permission issues, or malformed requests.
Links and References
- Vikunja API Documentation – Official API reference for understanding endpoints and payloads.
- Vikunja Project Management Tool – Main website for context about the platform.