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 task management API to update the position of a specific task within a project view. It is useful when you want to reorder tasks programmatically, for example, moving a task higher or lower in a list or changing its priority visually in a Kanban board or other project views.
Common scenarios include:
- Automatically reprioritizing tasks based on external triggers.
- Synchronizing task order between different tools.
- Adjusting task positions after bulk updates or imports.
Example: You have a project with multiple tasks displayed in a custom order. Using this node, you can move a task from position 5 to position 2 by specifying the new numeric position.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier (number) of the task whose position you want to update. |
| Project View ID | The identifier of the project view (e.g., a board or list) where the task position will be updated. This determines the context for the position change. |
| Task Position | A numeric value representing the new position of the task within the specified project view. Lower numbers typically mean higher priority or earlier placement. |
Output
The node outputs JSON data representing the updated task information as returned by the Vikunja API after repositioning. This typically includes the task's updated attributes such as its new position and possibly other metadata.
If the node supports binary data output, it would relate to any attachments or files associated with the task, but this operation primarily deals with JSON task data.
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 depends on the Vikunja REST API being accessible and the user having permissions to modify tasks and their positions.
Troubleshooting
- Invalid Task ID: If the provided Task ID does not exist, the API will return an error. Verify the task ID is correct and belongs to the specified project.
- Invalid Project View ID: Providing an incorrect or inaccessible project view ID will cause the update to fail. Ensure the view ID corresponds to a valid project view where the task exists.
- Position Value Issues: The position must be a valid number. Negative values or non-integers might cause errors or unexpected behavior.
- Authentication Errors: Missing or invalid API credentials will prevent the node from connecting to Vikunja. Check that the API key and base URL are correctly set.
- Permission Denied: The authenticated user must have rights to update tasks and their positions in the project.