Actions57
- Team Actions
- Webhook Actions
- 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
Overview
This node integrates with the Vikunja API to manage tasks and their related data. Specifically, for the Task - Delete a Comment operation, it allows users to delete a comment from a specified task by providing the task's ID and the comment's ID. This is useful in scenarios where comments on tasks need to be removed due to being outdated, irrelevant, or erroneous.
Practical examples include:
- Cleaning up task discussions by removing resolved or incorrect comments.
- Automating comment management as part of a workflow that updates task statuses or content.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task from which the comment will be deleted. |
| Comment ID | The unique numeric identifier of the comment to be deleted from the specified task. |
Output
The node outputs JSON data representing the result of the delete comment operation. Typically, this would confirm whether the deletion was successful or provide details about the deleted comment or any error encountered.
If the node supports binary data output (not indicated here), it would relate to attachments or media associated with tasks or comments, but for deleting a comment, only JSON output is relevant.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential configured in n8n.
- The base URL for the API must be set correctly in the node credentials.
- The node depends on the Vikunja API endpoints for tasks and comments management.
Troubleshooting
Common issues:
- Providing invalid or non-existent Task ID or Comment ID will cause errors.
- Insufficient permissions or invalid API credentials can lead to authorization failures.
- Network connectivity problems may prevent communication with the Vikunja API.
Error messages and resolutions:
- "Comment not found" — Verify that the Comment ID exists under the specified Task ID.
- "Unauthorized" or "Authentication failed" — Check that the API key credential is valid and has necessary permissions.
- "Invalid Task ID" — Confirm the Task ID is correct and the task exists.
- Timeout or network errors — Ensure stable internet connection and correct API endpoint URL.
Links and References
- Vikunja API Documentation — Official API reference for managing tasks and comments.
- n8n Documentation — General guidance on using credentials and HTTP request nodes.