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 task management API to update an existing task. It allows users to modify various attributes of a task such as its title, description, status (done or not), due dates, priority, color, and other metadata. This is useful in automation workflows where tasks need to be programmatically updated based on external triggers or conditions, for example:
- Automatically updating task progress or status when a related event occurs.
- Changing task deadlines or priorities dynamically based on project updates.
- Adding additional details or reassigning tasks without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to update (required). |
| Task Title | The new title/name of the task (required). |
| Description | A detailed description or notes about the task. |
| Done | Boolean indicating whether the task is completed. |
| Due Date Time | The deadline for the task, specified as a date-time in RFC3339 format. |
| Start Date Time | The start date and time for the task, in RFC3339 format. |
| End Date Time | The end date and time for the task, in RFC3339 format. |
| Task Color | Hexadecimal color code representing the task's color label. |
| Favorite | Boolean indicating if the task is marked as a favorite. |
| Priority | Numeric priority level from 1 (normal) to 5 (highest urgency). |
| Percent Done | Progress of the task expressed as a decimal between 0 (0%) and 1 (100%). |
| Repeat After | Number of seconds after which the task should repeat. |
| Repeat Mode | How the repeating task behaves: options include repeating after a set amount, monthly, or from current date. |
| Bucket ID | Identifier of the bucket (category/group) to assign the task to. |
Output
The node outputs JSON data representing the updated task object returned by the Vikunja API. This typically includes all the task's properties after the update, such as its ID, title, description, status, dates, priority, and any other metadata fields.
If the node supports binary data output, it would relate to attachments or files associated with the task, but this is not indicated in the provided source or properties.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node sends HTTP requests to the Vikunja REST API endpoints to perform updates.
Troubleshooting
- Invalid Task ID: If the task ID does not exist or is incorrect, the API will return an error. Verify the task ID before running the node.
- Authentication Errors: Ensure the API key and base URL are correctly configured in the credentials.
- Date Format Issues: Dates must be in valid RFC3339 format; otherwise, the API may reject the request.
- Permission Denied: The API user must have permission to update tasks; check user roles and access rights.
- Missing Required Fields: Task ID and Task Title are mandatory; omitting them will cause errors.