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
The node integrates with the Vikunja API to update an existing label. It allows users to modify a label's title, description, and color by specifying the label either through selection from a list or by providing its ID directly. This is useful in task and project management workflows where labels are used to categorize or prioritize items, enabling dynamic updates to labeling schemes without manual intervention.
Practical examples include:
- Automatically updating label colors based on project status changes.
- Renaming labels to reflect evolving terminology or priorities.
- Adding or modifying descriptions to provide more context for team members.
Properties
| Name | Meaning |
|---|---|
| Label Title or ID | The label to update. Choose from a searchable list of existing labels or specify the label ID directly. |
| Label Title | The new title/name for the label. |
| Description | A textual description providing additional information about the label. |
| Label Color | The color assigned to the label, specified as a hex color code (e.g., #000000 for black). |
Output
The node outputs JSON data representing the updated label object returned by the Vikunja API. This typically includes fields such as the label's ID, updated title, description, color, and possibly metadata like creation or modification timestamps.
If the node supports binary data output, it would relate to any file attachments or images associated with the label, but based on the provided code and properties, this node focuses solely on JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- Relies on the Vikunja REST API endpoints for labels (
/labels).
Troubleshooting
- Invalid Label ID: If the specified label ID does not exist, the API will likely return a 404 error. Ensure the label exists or select it from the list mode.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key and base URL are correctly set.
- Validation Errors: Omitting required fields like "Label Title" when updating may result in validation errors. Always provide all mandatory inputs.
- Network Issues: Connectivity problems with the Vikunja server can cause timeouts or connection errors. Check network access and server availability.