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 tasks, projects, labels, teams, and webhooks. Specifically, for the Task - Get Many operation, it fetches multiple tasks associated with a specified project. This is useful in scenarios where you want to list or process all tasks within a particular project, such as generating reports, syncing tasks with other tools, or automating task management workflows.
For example, you might use this node to:
- Retrieve all tasks from a project to display them in a dashboard.
- Export tasks from a project to another system.
- Automate notifications based on the current tasks in a project.
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. This determines which project's tasks will be retrieved. |
Output
The node outputs JSON data representing the tasks retrieved from the specified project. Each item in the output corresponds to a task object as returned by the Vikunja API, typically including fields such as task ID, title, description, status, due date, and other task-related metadata.
If the node supports binary data (not indicated here), it would represent attachments or files related to tasks, but this is not evident from the provided code.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL of the Vikunja instance must be configured in the node credentials.
- Uses internal helper functions to search and map projects for selection in the UI.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Specifying a non-existent project ID will result in no tasks being returned or an error.
- Network connectivity problems to the Vikunja server will cause request failures.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- "Project not found" or empty results suggest checking the project ID or selecting a valid project from the list.
- Timeout or network errors require checking the API URL and network access.