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 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 based on priority or workflow changes. Practical scenarios include automating task prioritization after certain triggers or syncing task order from another system.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task to update. |
| Project Title or ID | The project containing the task. You can select a project from a list or specify its ID directly. |
| Project View ID | The specific view within the project where the task position will be updated. Select from a list or provide an ID. |
| Task Position | A numeric value representing the new position of the task within the selected project view. |
Output
The node outputs JSON data representing the updated task information as returned by the Vikunja API after changing its position. This typically includes the task's details such as its ID, updated position, and other metadata. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Uses internal helper methods to search projects and project views for selection lists.
Troubleshooting
Common issues:
- Invalid or missing Task ID or Project/View IDs may cause errors.
- Incorrect API URL or expired/invalid API key will result in authentication failures.
- Providing a task position that is out of range might not reorder as expected.
Error messages:
- Authentication errors indicate problems with the API key or URL configuration.
- "Task not found" or similar errors suggest incorrect Task ID or project context.
- Validation errors if required parameters are missing.
Resolutions:
- Verify all IDs and ensure they exist in the Vikunja instance.
- Check API credentials and endpoint URL.
- Use the provided search dropdowns to avoid manual entry errors.