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 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.
Typical use cases include:
- Renaming a bucket to better reflect its purpose.
- Adjusting the maximum number of tasks allowed in a bucket to control workload.
- Reordering buckets to change their display sequence on the Kanban board.
For example, a user managing a software development project might update the "In Progress" bucket to increase its task limit or move it to a different position to reflect changes in workflow priorities.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. Can be selected from a searchable list or specified by its ID. |
| Project View ID | The specific project view (Kanban board) containing the bucket to update, identified by its 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 horizontal position; lower values appear left, higher values right. |
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 about the update operation.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the bucket, but this node primarily deals with JSON data.
Dependencies
- Requires an active connection to the Vikunja API via an API URL and an API authentication token configured in n8n credentials.
- The node depends on the Vikunja API endpoints for projects, project views, and buckets.
- No additional external services are required beyond the Vikunja instance.
Troubleshooting
- Invalid Project or View ID: If the provided project or view ID does not exist or the user lacks access, the API will return an error. Verify IDs and permissions.
- Bucket Not Found: Providing an incorrect bucket ID will cause the update to fail. Ensure the bucket ID corresponds to an existing bucket in the specified project view.
- Validation Errors: Omitting required fields like bucket title or providing invalid values (e.g., negative limits) may result in validation errors. Check input values carefully.
- API Connection Issues: Network problems or incorrect API URL/credentials will prevent communication with Vikunja. Confirm connectivity and credential correctness.
- Rate Limits or Quotas: Excessive requests might trigger rate limiting by the API. Implement retries or backoff strategies if needed.