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
The node integrates with the Vikunja API to retrieve data related to tasks, projects, labels, teams, and webhooks. Specifically, for the Task - Get operation, it fetches detailed information about a single task identified by its Task ID. This is useful in automation workflows where you need to access or manipulate task details from Vikunja, such as syncing task data with other tools, generating reports, or triggering actions based on task status.
Practical example:
You might use this node to get the details of a specific task when a user inputs a Task ID, then use that data to update a project management dashboard or notify team members about task progress.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task to retrieve. Required for fetching the task. |
Output
The node outputs JSON data representing the full details of the requested task. This typically includes fields such as task title, description, status, due date, assigned users, labels, comments, and other metadata defined by Vikunja's API.
If the node supports binary data output (not evident from the provided code), it would represent attachments or files associated with the task, but no such indication is present here.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the Vikunja API must be set correctly in the credentials configuration.
Troubleshooting
Common issues:
- Invalid or missing Task ID will cause the request to fail.
- Incorrect API URL or network connectivity problems can prevent successful API calls.
- Missing or invalid API authentication token will result in authorization errors.
Error messages:
- "Task not found" — Verify the Task ID exists in Vikunja.
- "Unauthorized" or "Authentication failed" — Check API credentials.
- "Network error" — Confirm the API URL and network access.
Resolving these usually involves verifying input parameters, checking credential setup, and ensuring the Vikunja server is reachable.
Links and References
- Vikunja API Documentation – Official API reference for understanding available endpoints and data structures.
- n8n Documentation – For general guidance on using n8n nodes and managing credentials.