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
This node integrates with the Vikunja API to retrieve various data related to task management. Specifically, for the "Task" resource and the "Get All Labels" operation, it fetches all labels associated with a given task. This is useful in scenarios where you want to programmatically access or display all tags/labels assigned to a specific task within Vikunja, such as for reporting, filtering, or automation workflows.
Practical examples:
- Automatically gather all labels on a task to categorize or prioritize tasks in an external system.
- Use the labels to trigger conditional logic in an automation workflow based on task tagging.
- Synchronize task labels with another project management tool.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task for which all associated labels will be retrieved. |
Output
The node outputs JSON data containing the list of labels linked to the specified task. Each label typically includes properties such as its name, color, and ID (based on typical Vikunja label structure). This output can be used downstream in workflows to process or analyze task labels.
If the node supports binary data output, it is not relevant for this operation since labels are textual metadata.
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 depends on the Vikunja REST API being accessible and the user having permission to read task labels.
Troubleshooting
Common issues:
- Invalid or missing Task ID: The node requires a valid numeric Task ID; ensure this is provided.
- Authentication errors: Verify that the API key and base URL are correctly set in the credentials.
- Network or API endpoint errors: Confirm the Vikunja server is reachable and the API endpoint
/tasks/{taskId}/labelsis available.
Error messages:
- Unauthorized or 401 errors indicate invalid or expired API credentials.
- 404 Not Found may mean the task does not exist or the user lacks permission.
- Validation errors if Task ID is missing or not a number.
Resolving these usually involves checking input parameters, credentials, and network connectivity.