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 drives remotely. Specifically, for the Drive - List operation, it retrieves a list of accessible drives associated with a specified account ID. This is useful when you want to programmatically access all drives available under a user’s account, for example, to display them in an interface or to automate further file management tasks.

Practical examples:

  • Automatically fetching all drives linked to a user account to sync or back up data.
  • Listing drives before selecting one to upload or download files.
  • Integrating with other workflows that require knowledge of available drives on kDrive.

Properties

Name Meaning
Account ID ID of the account (can be found in profile information). This identifies which user's drives to list.

Output

The output is a JSON object representing the list of drives accessible by the specified account. The exact structure depends on the kDrive API response but typically includes drive metadata such as drive IDs, names, and possibly other attributes describing each drive.

Example output structure (simplified):

{
  "drives": [
    {
      "id": "drive1",
      "name": "Personal Drive",
      ...
    },
    {
      "id": "drive2",
      "name": "Work Drive",
      ...
    }
  ]
}

No binary data is output for this operation.

Dependencies

  • Requires an API authentication token credential for kDrive (an API key or OAuth token).
  • The node makes HTTP requests to the kDrive API endpoint at https://api.infomaniak.com/2.
  • Proper configuration of the kDrive API credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired API token: The request will fail authorization; ensure the API token is valid and has sufficient permissions.
    • Incorrect Account ID: If the account ID does not exist or is mistyped, the API may return an empty list or an error.
    • Network connectivity problems can cause request failures.
  • Error messages:

    • Authorization errors typically indicate issues with the API token.
    • HTTP errors from the API (e.g., 400 or 404) suggest invalid parameters like the account ID.

To resolve these:

  • Verify the API credentials are correctly set up and active.
  • Confirm the account ID is correct by checking the user profile information.
  • Check network connectivity and retry.

Links and References

Discussion