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 retrieve various data related to project management. Specifically, for the Project resource and the Get All Project Views operation, it fetches all views associated with a given project. This is useful when you want to programmatically access different perspectives or filtered lists of tasks within a project, such as custom task views or saved filters.
Common scenarios include:
- Automating reporting by extracting all project views to analyze how tasks are organized.
- Syncing project views with other tools or dashboards.
- Dynamically presenting available views in a user interface based on the project context.
Example: You have a project "Website Redesign" and want to list all its views (e.g., "Backlog", "In Progress", "Completed") to allow users to select which view to display in a custom app.
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. This identifies which project's views will be retrieved. |
Output
The node outputs JSON data containing an array of all project views for the specified project. Each item in the array represents a single project view, typically including details such as the view's ID, name, filters, sorting options, and other metadata defining that view.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the views, but this operation primarily returns structured JSON data.
Dependencies
- Requires connection to a Vikunja instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL of the Vikunja API must be set correctly in the credentials.
Troubleshooting
- Invalid Project ID or Not Found: If the specified project does not exist or the ID is incorrect, the node may return an error or empty result. Verify the project ID or use the list mode to select a valid project.
- Authentication Errors: Ensure the API key or token is valid and has sufficient permissions to read project views.
- Network Issues: Confirm that the Vikunja API URL is reachable from the n8n environment.
- Empty Results: If no views are returned, the project might not have any defined views; verify in the Vikunja UI.