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 resource and the Get All Comments operation, it fetches all comments associated with a given task. This is useful in scenarios where users want to aggregate or analyze all discussions or notes attached to a particular task within Vikunja.
Practical examples include:
- Displaying all comments on a task in a dashboard.
- Exporting task comments for reporting or auditing purposes.
- Triggering workflows based on the content or presence of comments on tasks.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique numeric identifier of the task whose comments you want to retrieve. Required. |
Output
The node outputs JSON data containing all comments related to the specified task. Each comment typically includes details such as the comment text, author information, timestamps, and possibly other metadata defined by the Vikunja API.
If the node supports binary data output (not indicated here), it would represent attachments or media linked to comments, but this is not evident from the provided code.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- Relies on the Vikunja REST API being accessible and operational.
Troubleshooting
Common issues:
- Invalid or missing Task ID: The node requires a valid numeric Task ID; providing an incorrect or empty value will cause errors.
- Authentication failures: Incorrect or expired API credentials will prevent successful API calls.
- Network or API endpoint issues: If the Vikunja server is unreachable or returns errors, the node will fail to retrieve comments.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up and has necessary permissions.
- "Task not found" or similar: Verify that the Task ID exists in Vikunja.
- Timeout or network errors: Ensure the Vikunja API URL is correct and the server is reachable.