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 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 systems, generating reports, or triggering actions based on task status.
Practical examples:
- Automatically retrieving task details when a new comment is added elsewhere.
- Fetching task metadata to update a project management dashboard.
- Using task information to trigger notifications or reminders.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task to retrieve. Required for operations including get, delete, update, assignUser, unassignUser, addComment, updateComment, deleteComment, getAllComments, getAllLabelsOnTask, addLabel, removeLabel, addRelation, removeRelation, and updateTaskPosition. |
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 as provided by the Vikunja API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Vikunja API via an API URL and an API authentication token configured in the node credentials.
- The base URL for API requests is derived from the user-provided API URL credential, ensuring no trailing slash.
- The node expects JSON responses and sends JSON payloads.
Troubleshooting
- Common issues:
- Invalid or missing Task ID will cause the API request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent reaching the Vikunja API endpoint.
- Error messages:
- Authentication failures usually indicate invalid API keys or tokens; verify and update credentials.
- "Not Found" errors suggest the specified Task ID does not exist; confirm the ID is correct.
- Timeout or network errors require checking internet connection and API server availability.
Links and References
- Vikunja API Documentation – Official API reference for understanding available endpoints and data structures.
- n8n Documentation – For general guidance on using custom nodes and managing credentials.