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 update a specific Project View within a chosen project. It allows users to modify attributes of an existing project view such as its title, type (kind), bucket configuration mode, and additional settings like default or done bucket IDs and filters.
Common scenarios include:
- Renaming or reconfiguring a project view to better organize tasks.
- Changing the visualization style of a project view (e.g., switching from list to Kanban).
- Adjusting how buckets are managed in the view, such as setting a default bucket for new tasks or defining which bucket marks tasks as done.
- Applying filters to control which tasks appear in the view.
Practical example:
A project manager wants to update the "Sprint Backlog" view in their project to use a Kanban board instead of a list and set a specific bucket as the "Done" bucket. This node can perform that update programmatically.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. Can be selected from a searchable list of projects or specified directly by its ID. |
| Project View ID | The identifier of the project view to update. Must be provided as an ID string. |
| Project View Title | The new title for the project view. This is a required field when updating the view. |
| View Kind | The type of the project view. Options include: List, Gantt, Table, Kanban. Determines how tasks are visually organized in the view. |
| Bucket Configuration Mode | Defines how buckets are configured in the view. Options: None (no buckets), Manual (user-defined buckets), Filter (buckets defined by filters). |
| Additional Fields (Options) | A collection of optional settings: |
| - Default Bucket ID | Numeric ID of the bucket where new tasks without a bucket are added. Defaults to the leftmost bucket if not set. |
| - Done Bucket ID | Numeric ID of the bucket considered as "done". Tasks moved here are marked done; tasks marked done individually move here automatically. |
| - Project View Filter | A string filter applied to the project view to limit visible tasks based on criteria. |
Output
The node outputs JSON data representing the updated project view object returned by the Vikunja API. This typically includes all properties of the project view such as its ID, title, kind, bucket configuration, and any other metadata reflecting the current state after the update.
No binary data output is involved.
Dependencies
- Requires an active connection to the Vikunja API endpoint.
- Needs an API authentication token or key credential configured in n8n to authorize requests.
- The base URL for the API must be set correctly in the node credentials.
- The node uses HTTP requests with JSON payloads to interact with the Vikunja API.
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 listing projects and views before updating.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is valid and has sufficient permissions.
- Required Fields Missing: Omitting mandatory fields like the project view title or kind may result in validation errors. Always provide required inputs.
- API Endpoint Misconfiguration: Incorrect base URL or network issues can prevent communication with the Vikunja server. Confirm the API URL and network connectivity.
- Bucket IDs Invalid: Specifying bucket IDs that do not belong to the project may cause errors. Use valid bucket IDs associated with the project.