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 detailed information about a specific task. It is useful in scenarios where you need to fetch and process task data from Vikunja within an automated workflow, such as syncing tasks with other tools, generating reports, or triggering actions based on task details.
For example, you might use this node to get the current status, description, or due date of a task by its ID, then update another system or notify team members accordingly.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task to retrieve. This property is required. |
Output
The node outputs JSON data representing the full details of the requested task as returned by the Vikunja API. This typically includes fields such as task title, description, status, due date, labels, assigned users, and other metadata associated with the task.
No binary data output is produced by this operation.
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.
- The node sends HTTP requests to the Vikunja REST API endpoints.
Troubleshooting
- Invalid Task ID: If the provided Task ID does not exist, the API will likely return a 404 error. Verify that the Task ID is correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access task data.
- Network Issues: Confirm that the Vikunja server URL is reachable from the n8n environment.
- Malformed Requests: Check that the Task ID is a number and properly passed to the node.