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 manage tasks and their related data. Specifically, the "Add a Comment" operation under the "Task" resource allows users to add textual comments to an existing task in Vikunja. This is useful for collaboration scenarios where team members want to provide updates, feedback, or notes directly on tasks.
Practical examples include:
- Adding progress updates or clarifications to a task.
- Leaving instructions or additional context for other collaborators.
- Logging communication history related to a specific task.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to which the comment will be added. |
| Comment Text | The content of the comment to add. This is a multiline string representing the comment. |
Output
The node outputs JSON data representing the newly created comment object as returned by the Vikunja API. This typically includes details such as the comment's ID, text, author, creation timestamp, and possibly metadata related to the comment.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments linked to the comment, but this operation focuses on textual comments only.
Dependencies
- Requires an active connection to the Vikunja API via an API key or authentication token configured in n8n credentials.
- The base URL for the Vikunja instance must be correctly set in the node credentials.
- Network access to the Vikunja server is necessary.
Troubleshooting
Common issues:
- Invalid or missing Task ID: The node requires a valid numeric Task ID; providing an incorrect or non-existent ID will cause errors.
- Authentication failures: Incorrect or expired API credentials will prevent successful API calls.
- Network connectivity problems: Ensure the Vikunja server URL is reachable from the n8n environment.
Error messages:
- "Task not found" or similar indicates the Task ID does not exist.
- "Unauthorized" or "Authentication failed" suggests invalid API credentials.
- Timeout or network errors indicate connectivity issues.
To resolve these, verify the Task ID exists in Vikunja, confirm API credentials are correct and have sufficient permissions, and ensure network connectivity.