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, specifically enabling users to update existing tasks. It allows modifying various attributes of a task such as its title, description, due dates, priority, completion status, and more. This node is useful in automation workflows where task details need to be programmatically updated based on external triggers or data changes.
Practical examples include:
- Automatically updating task progress or status when related work is completed.
- Changing task priorities or deadlines based on project updates.
- Adding detailed descriptions or reassigning tasks dynamically.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to update (required). |
| Task Title | The new title for the task (required). |
| Bucket ID | The ID of the bucket to move the task into. |
| Description | A textual description providing more details about the task. |
| Done | Boolean indicating whether the task is marked as done. |
| Due Date Time | The due date and time for the task in RFC3339 format. |
| End Date Time | The end date and time for the task in RFC3339 format. |
| Favorite | Boolean indicating if the task is marked as a favorite. |
| Percent Done | Progress of the task expressed as a decimal between 0 and 1. |
| Priority | Task priority level from 1 (normal) to 5 (highest urgency). |
| Repeat After | Number of seconds after which the task repeats. |
| Repeat Mode | How the repeating task behaves; options are: |
- Repeat After Amount (repeat after Repeat After seconds) |
|
- Repeat Monthly (repeat all dates monthly, ignoring Repeat After) |
|
| - Repeat From Current Date (repeat from current date instead of last set date) | |
| Start Date Time | The start date and time for the task in RFC3339 format. |
| Task Color | Hex color code representing the task's color label. |
Output
The node outputs JSON data representing the updated task object returned by the Vikunja API. This includes all task fields such as ID, title, description, status flags, dates, priority, and any other metadata associated with the task after the update operation.
If binary data were involved (not indicated here), it would typically represent attachments or files related to the task, but this node focuses on JSON task data only.
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 with JSON payloads to the Vikunja REST API endpoints.
Troubleshooting
- Missing or invalid Task ID: The update will fail if the Task ID is not provided or does not exist. Ensure the correct numeric ID is supplied.
- Invalid date formats: Dates must be in RFC3339 format; otherwise, the API may reject the request.
- Permission errors: If the API key lacks permissions to update tasks, the node will return authorization errors.
- Network issues: Connectivity problems to the Vikunja server will cause request failures.
- Invalid property values: For example, setting priority outside 1-5 or percent done outside 0-1 range may cause errors.
To resolve these:
- Double-check input values and formats.
- Verify API credentials and permissions.
- Confirm network connectivity and correct API URL.