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 a Kanban bucket within a specific project view. It allows users to modify properties of an existing bucket such as its title, task limit, and position in the Kanban board.
Typical use cases include:
- Renaming a bucket to better reflect its purpose.
- Adjusting the maximum number of tasks allowed in a bucket to manage workload.
- Reordering buckets on the Kanban board by changing their position value.
For example, a project manager might use this node to rename a "To Do" bucket to "Backlog," increase its task limit from 10 to 20, and move it to the far left of the board by setting its position to 0.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project containing the bucket. Can be selected from a searchable list or specified directly by ID. |
| Project View ID | The specific project view (Kanban board) where the bucket exists. Selectable from a list or by ID. |
| Bucket ID | The unique numeric identifier of the bucket to update. |
| Bucket Title | The new title/name for the bucket. |
| Limit | The maximum number of tasks allowed in this bucket. |
| Bucket Position | Numeric value determining the bucket's order on the Kanban board; lower numbers appear more to the left. |
Output
The node outputs JSON data representing the updated bucket object returned by the Vikunja API. This typically includes fields such as the bucket's ID, title, limit, position, and possibly metadata like timestamps or related project/view IDs.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- The node uses HTTP requests to interact with the Vikunja REST API endpoints.
Troubleshooting
- Invalid Project or View ID: If the provided project or view ID does not exist or is inaccessible, the API will return an error. Verify that the IDs are correct and that the API key has sufficient permissions.
- Bucket Not Found: Providing an incorrect bucket ID will cause the update to fail. Confirm the bucket ID corresponds to an existing bucket in the specified project view.
- Permission Denied: Insufficient API permissions can result in authorization errors. Ensure the API key has rights to modify projects and buckets.
- Invalid Field Values: Setting invalid values (e.g., negative limits or positions) may cause validation errors. Use sensible positive integers for limit and position.
- Network Issues: Connectivity problems to the Vikunja server will prevent updates. Check network access and API URL correctness.