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 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 workflows.
- 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 certain condition is met in your workflow.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. You can select from a list of projects or specify a project ID directly. |
| Project View ID | The specific project view (Kanban board) within the project where the bucket will be created. Must be specified 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 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.
If the node supports binary data output, it would relate to attachments or files associated with the bucket, but this operation primarily deals with JSON data describing the bucket.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the Vikunja instance must be set correctly in the node credentials.
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 authorization failures. Ensure the API key/token is valid and has sufficient permissions.
- Bucket Title Required: Omitting the bucket title will result in validation errors. Always provide a non-empty string.
- Limit and Position Values: Providing negative numbers or invalid types for limit or position may cause errors or unexpected behavior. Use zero or positive integers.
- API Connectivity Issues: Network problems or incorrect base URL configuration can prevent successful API calls.