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 API to update a Kanban bucket within a specified project view. It allows users to modify properties of an existing bucket such as its title, task limit, and position on the board. This is useful in project management workflows where organizing tasks visually in buckets (columns) helps track progress or categorize work.
Practical examples include:
- Renaming a bucket to reflect a new phase in a project.
- Adjusting the maximum number of tasks allowed in a bucket to control workload.
- Reordering buckets to prioritize certain stages or categories.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. Can be selected from a list of projects or specified by its ID. |
| Project View ID | The specific project view (board) containing the bucket to update, identified by its ID. |
| Bucket ID | The unique 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 horizontal position; lower values appear left, higher right. |
Output
The node outputs JSON data representing the updated bucket object returned by the Vikunja API. This typically includes the bucket's ID, title, limit, position, and possibly metadata about the update operation. There is no binary output.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the Vikunja instance must be set correctly in the credentials.
Troubleshooting
- Invalid Project or View ID: If the provided project or view ID does not exist or is incorrect, the API will return an error. Verify IDs are correct and accessible.
- Bucket Not Found: Providing a non-existent bucket ID will cause failure. Confirm the bucket ID belongs to the specified project view.
- Permission Issues: Insufficient permissions or invalid API tokens can lead to authorization errors. Ensure the API key has rights to modify projects and buckets.
- Validation Errors: Omitting required fields like bucket title or providing invalid values (e.g., negative limits) may cause validation errors. Double-check input values.
- API Connectivity: Network issues or incorrect base URL settings can prevent communication with the Vikunja API.