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 data related to projects, tasks, labels, teams, and webhooks. Specifically, for the Project - Get operation, it fetches detailed information about a single project identified either by its title or ID. This is useful in scenarios where you want to access project metadata or details within an automation workflow, such as syncing project info to another system, generating reports, or triggering actions based on project attributes.
Practical examples include:
- Retrieving a project's details to display in a dashboard.
- Using project information to create linked tasks or notifications.
- Automating updates or audits based on project properties.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The identifier of 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 from a dynamically searchable list of available projects.
- ID: Provide the exact project ID as a string.
Output
The node outputs JSON data representing the full details of the requested project as returned by the Vikunja API. This typically includes fields such as project ID, title, description, creation date, update date, and other metadata relevant to the project.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- Network access to the Vikunja server hosting the API.
Troubleshooting
- Invalid Project ID or Not Found: If the specified project ID does not exist or is incorrect, the node may return an error indicating the project was not found. Verify the project ID or use the list mode to select a valid project.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
- Network Issues: Connectivity problems to the Vikunja API endpoint will result in request timeouts or connection errors. Check network settings and API availability.
- Permission Denied: Insufficient permissions for the API key to access project data can cause authorization errors. Confirm that the API key has the necessary scopes or roles.