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 their labels. Specifically, the "Remove a Label From a Task" operation allows users to detach a label from a specified task within Vikunja. This is useful in scenarios where task categorization or tagging needs updating, such as removing outdated or incorrect labels from tasks to keep project management organized.
Practical examples include:
- Removing a "High Priority" label from a task once it no longer applies.
- Detaching a "Bug" label after an issue has been resolved.
- Cleaning up task labels during project review or reorganization.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task from which the label will be removed. |
| Label Title or ID | The label to remove from the task. Can be selected from a searchable list of existing labels or specified directly by its ID. |
Output
The node outputs JSON data representing the result of the label removal operation. Typically, this includes confirmation that the label was successfully removed from the task or details about the updated task state. The exact structure depends on the Vikunja API response but generally confirms the action's success.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- The node expects the base URL of the Vikunja instance to be configured in the credentials.
- Uses HTTP headers to accept and send JSON-formatted data.
Troubleshooting
- Invalid Task ID: If the provided Task ID does not exist, the API may return an error indicating the task was not found. Verify the Task ID is correct.
- Invalid Label ID: Providing a non-existent label ID or title can cause failure. Ensure the label exists or select it from the provided searchable list.
- Authentication Errors: Missing or invalid API credentials will prevent the node from connecting to Vikunja. Confirm that the API key and base URL are correctly set.
- Network Issues: Connectivity problems to the Vikunja server will cause request failures. Check network access and server availability.
- Permission Denied: The API user must have sufficient permissions to modify tasks and labels. Lack of permissions will result in authorization errors.
Links and References
- Vikunja API Documentation – Official API reference for understanding endpoints and payloads.
- Vikunja Project Management Tool – Main website for the Vikunja task management system.