Actions57
- Team Actions
- Webhook Actions
- 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
Overview
This node integrates with the Vikunja API to update the position of a specific task within a project view. It is useful in scenarios where tasks need to be reordered or reprioritized programmatically, such as automating task management workflows or syncing task order from other systems.
For example, you might use this node to move a task higher or lower in a Kanban board or list view after certain triggers, ensuring that task priorities are reflected accurately without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task to update. |
| Project View ID | The identifier of the project view (e.g., a specific board or list) where the task resides. This determines the context for positioning. |
| 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.
No binary data output is involved.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL of the Vikunja instance must be set correctly in the node credentials.
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 accessible.
- Invalid Project View ID: Providing an incorrect or inaccessible project view identifier will cause the update to fail. Ensure the view ID corresponds to a valid project view.
- Permission Issues: Insufficient permissions on the API key or user may result in authorization errors. Confirm the API token has rights to modify tasks.
- Position Value Errors: Supplying a non-numeric or out-of-range position value may cause unexpected behavior or errors. Use valid numeric positions within the expected range.
- API Connectivity: Network issues or incorrect base URL configuration can prevent successful API calls. Check connectivity and credential settings.
Links and References
- Vikunja API Documentation – Official API reference for task and project operations.
- n8n Documentation – General guidance on setting up credentials and using HTTP-based nodes.