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
- Team Actions
- Task Actions
- Webhook Actions
Overview
This node interacts with the Vikunja API to retrieve various data related to projects, tasks, labels, teams, and webhooks. Specifically, for the "Project" resource and the "Get All Project Views" operation, it fetches all views associated with a specified project. This is useful when you want to programmatically access different saved views or filters configured within a project in Vikunja.
Practical examples include:
- Automating the retrieval of all custom views for a project to display or process them elsewhere.
- Integrating project views into dashboards or reporting tools.
- Synchronizing project view configurations between environments.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to operate on. You can select a project from a searchable list or specify its ID directly. |
The property supports two modes:
- From List: Select a project interactively from a searchable dropdown.
- ID: Provide the project ID as a string.
Output
The output JSON contains an array of project views associated with the specified project. Each item in the array represents a single project view object retrieved from the Vikunja API endpoint /projects/{projectId}/views.
The structure typically includes details such as view identifiers, names, filters, sorting options, or other metadata defining each view. The exact fields depend on Vikunja's API response schema for project views.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token credential configured in n8n (referred generically as an API key credential).
- The base URL for the Vikunja instance must be set correctly in the credentials.
Troubleshooting
Common issues:
- Invalid or missing project ID: Ensure the project exists and the ID is correct.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network connectivity problems: Confirm that the Vikunja server is reachable from the n8n environment.
Error messages:
- 404 Not Found: The specified project does not exist or the user lacks access.
- 401 Unauthorized: Authentication failed due to invalid or missing credentials.
- 500 Internal Server Error: Server-side issue; retry later or check Vikunja server logs.
Resolving these usually involves verifying input parameters, checking credentials, and ensuring network accessibility.