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 integrates with the Vikunja API to retrieve information about projects. Specifically, the "Get" operation under the "Project" resource fetches details of a single project by its title or ID. This is useful in workflows where you need to access project metadata or verify project existence before performing further actions such as task creation, updates, or reporting.
Practical examples include:
- Fetching project details to display in a dashboard.
- Validating a project’s existence before adding tasks.
- Synchronizing project data between Vikunja and other tools.
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. |
The property supports two modes:
- From List: Select a project interactively from a searchable dropdown.
- ID: Provide the exact project ID as a string.
Output
The node outputs JSON data representing the project details retrieved from Vikunja's API. This typically includes fields such as project ID, title, description, creation date, and other metadata defined by Vikunja for a project entity.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests with JSON content type headers.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an incorrect project ID or selecting a non-existent project will result in not found errors.
- Network connectivity problems may prevent the node from reaching the Vikunja API.
Error messages:
- Authentication failures: Check that the API key is valid and correctly configured.
- 404 Not Found: Verify the project ID or selection is correct and exists in Vikunja.
- Timeout or network errors: Ensure the API URL is reachable and there are no firewall restrictions.