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 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 an external 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 identifier (number) of the task for which all comments should be retrieved. |
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 evident from the provided code), it would relate to attachments or media within comments, but this is not indicated here.
Dependencies
- Requires an API key credential to authenticate requests against the Vikunja API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the Vikunja REST API being accessible and properly configured.
Troubleshooting
Common issues:
- Invalid or missing Task ID will cause the request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent access to the Vikunja API.
- If the task has no comments, the output may be empty or contain an empty array.
Error messages:
- Authentication errors usually indicate invalid API keys; verify and update credentials.
- "Not Found" errors suggest the Task ID does not exist; confirm the ID is correct.
- Rate limiting or server errors require checking API usage limits or Vikunja server status.