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 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 categorize or prioritize tasks in an external system.
- Syncing task labels from Vikunja to another project management tool.
- Triggering actions based on the presence of certain labels on a task.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier (number) of the task whose labels you want to retrieve. Required. |
Output
The node outputs JSON data containing the list of labels associated with the specified task. Each label object typically includes properties such as label name, color, ID, and possibly other metadata defined by the Vikunja API.
If the node supports binary data output (not indicated here), it would represent any file attachments or media related to labels, but this operation primarily returns JSON label data.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential configured in n8n.
- The base URL for the Vikunja API must be set correctly in the node credentials.
- Internet access to reach the Vikunja server.
Troubleshooting
Common issues:
- Invalid or missing Task ID: Ensure the Task ID is provided and corresponds to an existing task.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network errors: Check connectivity to the Vikunja API endpoint.
- API URL misconfiguration: Confirm the base URL does not have trailing slashes or typos.
Error messages:
- Unauthorized or 401 errors indicate invalid API credentials.
- 404 Not Found may mean the task ID does not exist.
- Timeout or network errors suggest connectivity problems.
Resolving these usually involves verifying input parameters, credentials, and network settings.