Actions57
- Team Actions
- Webhook Actions
- 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
Task → Get Many
AI-generatedOverview
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. |
The property supports two modes:
- From List: Select a project by searching through available projects.
- ID: Provide the exact project ID manually.
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 like task ID, title, description, status, due date, and other task-related metadata.
If the node supports binary data (not indicated here), it would be summarized accordingly, but this node primarily outputs JSON task data.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Uses internal helper methods to search and map projects for the resource locator input.
Troubleshooting
- Invalid Project ID or Not Found: If the provided project ID does not exist or is incorrect, the node will fail to retrieve tasks. Verify the project ID or select the project from the list mode.
- Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions to access the project's tasks.
- Empty Results: If no tasks are returned, confirm that the project contains tasks and that filters (if any) are not excluding all tasks.
- API Connectivity Issues: Check network connectivity and the correctness of the Vikunja API base URL.
Links and References
- Vikunja Official Website
- Vikunja API Documentation (for detailed API endpoints and data structures)