Actions57
- Team Actions
- Webhook Actions
- 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
Overview
This node integrates with the Vikunja API to manage tasks and their associated labels. Specifically, the "Add a Label" operation for the "Task" resource allows users to attach an existing label to a specified task by providing the task's ID and the label's title or ID. This is useful in scenarios where tasks need categorization or tagging to improve organization, filtering, and tracking within project management workflows.
Practical examples include:
- Automatically tagging newly created tasks with priority or status labels.
- Adding contextual labels to tasks based on user input or external triggers.
- Organizing tasks visually by labels for better team collaboration.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task to which the label will be added. |
| Label Title or ID | The label to add to the task. Can be selected from a searchable list of existing labels or specified directly by its ID. |
Output
The node outputs JSON data representing the result of the label addition operation. Typically, this includes confirmation that the label was successfully attached to the task, along with any updated task information returned by the Vikunja API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task or label, but this operation focuses on JSON metadata only.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential.
- The base URL for the API must be configured in the node credentials.
- The node depends on the Vikunja API endpoints for tasks and labels, specifically the endpoint to add a label to a task.
- No additional external services are required beyond the Vikunja API.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Task ID or Label ID will cause the operation to fail.
- Network connectivity issues or incorrect API base URL configuration can prevent successful API calls.
- Insufficient permissions or invalid API credentials may result in authorization errors.
Error Messages:
- "Task not found" — Verify the Task ID is correct and the task exists.
- "Label not found" — Ensure the label exists and the correct ID or title is used.
- "Unauthorized" or "Forbidden" — Check API credentials and permissions.
- "Network Error" — Confirm network access and API URL correctness.
Resolving these typically involves verifying input values, checking API credentials, and ensuring the Vikunja server is reachable.
Links and References
- Vikunja API Documentation
- Vikunja Official Website
- n8n Documentation on Creating Custom Nodes