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 create a new label resource. It allows users to define a label's title, description, and color, which can be used to categorize or tag tasks and projects within Vikunja. This is useful in task management workflows where organizing items by labels improves clarity and filtering.
Practical examples include:
- Automatically creating labels for different priority levels (e.g., High, Medium, Low) when setting up a project.
- Adding descriptive labels with specific colors to visually distinguish task categories.
- Generating labels dynamically based on external input or triggers in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Label Title | The name/title of the label to create. |
| Description | A textual description providing more details about the label. |
| Label Color | The color of the label represented as a hex color code (e.g., #FF0000 for red). |
Output
The node outputs JSON data representing the newly created label object as returned by the Vikunja API. This typically includes fields such as the label's unique identifier, title, description, color, and possibly metadata like creation timestamps.
If the node supports binary data output, it would relate to any file or media associated with the label, but based on the provided code and properties, this node focuses solely on JSON data output.
Dependencies
- Requires access to the Vikunja API endpoint, configured via an API URL credential.
- Needs an API authentication token or key credential to authorize requests to Vikunja.
- The node expects the base URL of the Vikunja instance to be set correctly in the credentials.
- Network connectivity to the Vikunja server is necessary.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect API URL configuration may lead to connection errors.
- Providing an empty or invalid label title will likely result in validation errors from the API.
- Error messages:
- Authentication errors usually indicate problems with the API key/token; verify credentials.
- HTTP 404 or connection refused errors suggest incorrect API URL or network issues.
- Validation errors from the API will specify missing required fields or invalid formats; ensure all required properties are correctly filled.