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
This 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, due dates, priority, completion status, and more. This is useful in automation workflows where tasks 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 deadlines or priorities based on project updates.
- Adding additional metadata like colors or labels to 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 detailed description of the task. |
| Done | Whether the task is marked as done (true/false). |
| 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 | Whether the task is marked as a favorite (true/false). |
| 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: - Repeat After Amount - Repeat Monthly - Repeat From Current 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. |
Output
The node outputs JSON data representing the updated task object returned by the Vikunja API. This typically includes all task properties such as ID, title, description, status flags, dates, priority, and any other metadata that was updated or present before.
If the API supports binary data for tasks (e.g., attachments), this node would summarize it accordingly, but based on the provided information, the output is purely JSON.
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
- Common issues:
- Invalid or missing Task ID will cause the update to fail.
- Incorrect API URL or authentication token will result in authorization errors.
- Providing invalid date formats or out-of-range values for fields like priority or percent done may cause validation errors.
- Error messages:
- "Task not found" indicates the specified Task ID does not exist.
- "Unauthorized" or "Forbidden" suggests issues with API credentials.
- "Invalid input" points to malformed or unsupported property values; verify field types and formats.
To resolve these, ensure the Task ID exists, credentials are correct, and all inputs conform to expected formats.