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 multiple tasks associated with a specified project. It is designed to fetch many tasks at once, which is useful for workflows that need to process or analyze task lists from a particular project in Vikunja.
Common scenarios include:
- Automating reporting by extracting all tasks from a project.
- Synchronizing tasks between Vikunja and other tools.
- Bulk processing or filtering of tasks based on project context.
For example, you might use this node to get all tasks from a project named "Marketing Campaign" to generate a status report or to trigger follow-up actions on each task.
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 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 metadata.
No binary data output is indicated by the source code.
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.
- The node uses HTTP requests to communicate with the Vikunja API endpoints.
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 the API key credential is valid and has sufficient permissions to access the project's tasks.
- Network Issues: Connectivity problems to the Vikunja API endpoint may cause failures; check network settings and API URL configuration.
- Empty Results: If no tasks are returned, confirm that the project contains tasks and that filters (if any) are correctly set.