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 update a comment on a specific task. It allows users to modify the text of an existing comment identified by its Comment ID within a given Task ID. This is useful in scenarios where comments need correction, clarification, or additional information after they have been initially posted.
Practical examples:
- Updating a typo or error in a task comment.
- Adding more details or context to an existing comment without creating a new one.
- Moderating or sanitizing comments before sharing them with a wider team.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task containing the comment to be updated. |
| Comment ID | The unique identifier of the comment that needs to be updated. |
| Comment Text | The new text content for the comment. This replaces the existing comment's text. |
Output
The node outputs JSON data representing the updated comment object as returned by the Vikunja API. This typically includes fields such as the comment's ID, updated text, timestamps, and possibly user information related to the comment.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the comment, but this is not applicable based on the provided code.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- The node uses HTTP requests to interact with the Vikunja REST API endpoints.
Troubleshooting
- Missing or invalid Task ID or Comment ID: Ensure both IDs are correctly provided and correspond to existing entities in Vikunja.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- API endpoint errors: Check the base URL configuration and network connectivity to the Vikunja server.
- Empty or invalid Comment Text: The comment text must be non-empty; otherwise, the API may reject the update.
- Permission issues: The authenticated user must have rights to edit comments on the specified task.
Common error messages might include HTTP 401 Unauthorized, 404 Not Found (if task or comment does not exist), or 400 Bad Request (invalid input). Resolving these involves verifying credentials, IDs, and input data correctness.