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 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 where tasks are grouped. This operation is useful for organizing tasks visually by stages or categories within a project.
Common scenarios include:
- Structuring a project’s workflow by adding new buckets such as "To Do", "In Progress", or "Done".
- Dynamically creating buckets based on project needs or automation triggers.
- Managing task limits and ordering of buckets to reflect priority or process flow.
Example: Automatically add a new bucket named "Review" to a specific project view when a milestone is reached.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. Can be selected from a searchable list of projects or specified by ID. |
| Project View ID | The specific project view (Kanban board) within the project where the bucket will be created. Must be provided as an 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 Kanban board; lower values appear more left. |
Output
The node outputs JSON data representing the newly created Kanban bucket. This typically includes details such as the bucket's unique identifier, title, limit, position, and any other metadata returned by the Vikunja API about the bucket.
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 project view ID does not exist or is incorrect, the API will return an error. Verify IDs are correct and accessible.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set.
- Permission Issues: The authenticated user must have permission to modify the specified project and its views.
- Limit Value Errors: Providing a negative or non-numeric limit may cause validation errors.
- Position Conflicts: Overlapping bucket positions might affect display order; ensure unique numeric positions.
Links and References
- Vikunja API Documentation
- Kanban Board Concepts
- n8n Documentation on Creating Custom Nodes