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 information about a specific label. It is designed to fetch details of a label by either selecting it from a list or specifying its unique ID. This functionality is useful in scenarios where you want to automate workflows involving task categorization, filtering, or reporting based on labels within Vikunja.
For example, you might use this node to:
- Retrieve label details to dynamically assign tasks in another system.
- Fetch label metadata for generating reports or dashboards.
- Use label information as part of conditional logic in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Label Title or ID | The label to operate on. You can select a label from a searchable list or specify its ID directly. |
The "Label Title or ID" property supports two modes:
- From List: Choose a label from a searchable dropdown list populated from Vikunja.
- ID: Provide the exact ID of the label as a string.
Output
The node outputs JSON data representing the label's details as returned by the Vikunja API. This typically includes fields such as the label's ID, title, color, and any other metadata associated with the label.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node depends on the Vikunja API being accessible and responsive.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an incorrect label ID or selecting a non-existent label will result in not found errors.
- Network connectivity issues may prevent the node from reaching the Vikunja API.
Error Messages:
- Authentication failed: Check that the API key credential is correct and has necessary permissions.
- Label not found: Verify the label ID or selection is valid and exists in Vikunja.
- Request timeout or network error: Ensure the API URL is reachable and there are no firewall restrictions.