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 manage project-related data, specifically allowing users to create a Kanban bucket within a project view. A Kanban bucket is a container or column in a Kanban board that holds tasks, helping organize work visually by stages or categories.
Typical use cases include:
- Organizing tasks into different workflow stages (e.g., To Do, In Progress, Done) within a project.
- Structuring project views for better task management and visualization.
- Automating project setup by programmatically adding buckets to project views.
For example, a user can automate creating a new bucket called "Review" in a specific project view to represent tasks awaiting review.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project where the bucket will be created. Can be selected from a searchable list of projects or specified by ID. |
| Project View ID | The specific project view (like a Kanban board) within the project where the bucket will be added. Selectable from a list or by ID. |
| Bucket Title | The name/title of the new Kanban bucket to create. |
| Limit | The maximum number of tasks allowed in this bucket. |
| Bucket Position | Numeric value determining the bucket's position/order in the view; lower numbers appear left, higher numbers right. |
Output
The node outputs JSON data representing the newly created Kanban bucket. This typically includes details such as the bucket's ID, title, limit, position, and any other metadata returned by the Vikunja API upon creation.
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.
- Relies on the Vikunja REST API endpoints for projects, project views, and buckets.
Troubleshooting
- Invalid Project or View ID: If the provided project or project view ID does not exist or is incorrect, the API will return an error. Verify IDs by using the search options or directly checking in Vikunja.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to create buckets.
- Limit and Position Values: Providing invalid values (e.g., negative numbers) for limit or position may cause errors. Use sensible numeric values.
- Network Issues: Connectivity problems with the Vikunja server will prevent bucket creation. Check network access and API URL correctness.