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 delete a Kanban bucket within a project view. It is useful in scenarios where you want to programmatically remove a bucket (a column or category in a Kanban board) from a specific project view, for example, when cleaning up outdated workflow stages or reorganizing task boards.
Practical examples include:
- Automating project board maintenance by deleting obsolete buckets.
- Integrating with other tools to dynamically update project views based on external triggers.
- Managing multiple projects and their views efficiently through automation workflows.
Properties
Name | Meaning |
---|---|
Project Title or ID | The target project to operate on. You can select a project from a searchable list or specify its ID directly. |
Project View ID | The specific project view (e.g., a Kanban board layout) within the project where the bucket exists. Must be provided as an ID. |
Bucket ID | The numeric identifier of the Kanban bucket to delete within the specified project view. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the bucket was successfully deleted or provide error information if the operation failed.
If the node supports binary data output, it would relate to any file or media content returned by the API, but in this case, the operation focuses on deletion and thus primarily returns JSON status responses.
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 depends on the Vikunja REST API endpoints for projects, project views, and buckets.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent Project ID, Project View ID, or Bucket ID will cause the operation to fail.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Network connectivity problems to the Vikunja server can cause request failures.
Error messages:
- "Not Found" or similar indicates that the specified project, view, or bucket does not exist.
- "Unauthorized" or "Forbidden" suggests issues with API authentication or permissions.
- "Bad Request" may occur if required parameters are missing or malformed.
Resolutions:
- Verify all IDs are correct and correspond to existing resources.
- Ensure the API key credential is valid and has appropriate access rights.
- Check network connectivity and Vikunja server availability.
Links and References
- Vikunja API Documentation
- Kanban Board Concepts in Vikunja
- n8n Documentation on Creating Custom Nodes