kDrive icon

kDrive

Manipulate files from remote Kdrive

Actions6

Overview

This node integrates with the KDrive cloud storage service, allowing users to manipulate files and folders remotely. Specifically for the File - Delete operation, it deletes a specified file from a given drive in KDrive.

Common scenarios where this node is useful include:

  • Automating cleanup of files after processing.
  • Removing outdated or temporary files from cloud storage.
  • Integrating file deletion into larger workflows that manage cloud storage content.

For example, after downloading and processing a file, you can use this node to automatically delete the original file from KDrive to save space.

Properties

Name Meaning
Drive ID The unique identifier of the drive where the file resides.
File ID The unique identifier of the file to be deleted within the specified drive.

Output

The output JSON contains the response from the KDrive API after attempting to delete the file. This typically includes confirmation details about the deletion operation, such as status or metadata returned by the API.

No binary data is output for the delete operation.

Example output structure (simplified):

{
  "json": {
    // API response confirming deletion, e.g.:
    "status": "success",
    "fileId": "12345"
  }
}

Dependencies

  • Requires an active connection to the KDrive API using an API authentication token.
  • The node expects credentials configured with access rights to perform file deletions on the target KDrive account.
  • Network access to https://api.infomaniak.com/2 is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired API token: The node will fail to authenticate with the KDrive API.
    • Incorrect Drive ID or File ID: The API may return errors indicating the file or drive was not found.
    • Insufficient permissions: The authenticated user must have rights to delete files in the specified drive.

  • Error messages:

    • Errors from the API are propagated and may include HTTP status codes like 401 (Unauthorized), 404 (Not Found), or 403 (Forbidden).
    • To resolve, verify the API credentials, ensure the IDs are correct, and confirm the user has appropriate permissions.

Links and References

Discussion