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 retrieve various data related to task management, projects, labels, teams, and webhooks. 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 include:
- Automatically retrieving all labels on a task to trigger conditional logic based on label presence.
- Syncing task labels from Vikunja into another system or database.
- Displaying task labels in a custom dashboard or notification.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task for which all associated labels should be retrieved. |
Note: The "Task ID" property is required for this operation.
Output
The node outputs JSON data containing the list of labels associated with the specified task. Each label typically includes properties such as its name, color, and ID (based on typical label structures in task management APIs). The output structure allows downstream nodes to process or utilize these labels as needed.
If the node supports binary data output, it is not relevant for this operation since labels are textual metadata.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential configured in n8n.
- The base URL for the Vikunja instance must be provided in the credentials.
- The node uses standard HTTP headers for JSON communication.
Troubleshooting
- Missing or invalid Task ID: Ensure that the Task ID is provided and corresponds to an existing task in Vikunja.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network issues: Confirm that the Vikunja API URL is reachable from the n8n environment.
- Empty label list: If no labels are returned, verify that the task actually has labels assigned in Vikunja.
Common error messages might include unauthorized access, resource not found, or bad request due to missing parameters. Resolving these usually involves checking credentials, input parameters, and network connectivity.