Vikunja icon

Vikunja

Get data from Vikunja's API

Overview

This node integrates with the Vikunja API to manage tasks and their related data. Specifically, the "Delete a Comment" operation under the "Task" resource allows users to remove a comment from a specified task. This is useful in scenarios where comments are no longer relevant, were added by mistake, or need to be cleaned up for clarity.

Practical examples include:

  • Automating the removal of outdated or resolved discussion points on tasks.
  • Moderation workflows where inappropriate comments must be deleted.
  • Synchronizing comments between systems by deleting those that have been removed elsewhere.

Properties

Name Meaning
Task ID The unique identifier of the task from which the comment will be deleted.
Comment ID The unique identifier of the comment to delete from the specified task.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this includes confirmation of successful deletion or details about the deleted comment. Since this is a delete operation, the output mainly serves as an acknowledgment rather than returning the full comment data.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Vikunja API.
  • The node expects the base URL of the Vikunja instance to be configured in the credentials.
  • Network access to the Vikunja API endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing Task ID or Comment ID will cause the operation to fail.
    • Authentication errors if the API key credential is incorrect or expired.
    • Network connectivity issues preventing access to the Vikunja API.
    • Attempting to delete a comment that does not exist or has already been deleted.
  • Error Messages:

    • "404 Not Found" — The specified task or comment ID does not exist. Verify IDs.
    • "401 Unauthorized" — Authentication failed. Check API key validity.
    • "400 Bad Request" — Input parameters may be malformed or missing.
  • Resolutions:

    • Double-check the Task ID and Comment ID values.
    • Ensure the API key credential is correctly set and has sufficient permissions.
    • Confirm network connectivity and correct API base URL configuration.

Links and References

Discussion