kDrive

Overview

This node integrates with the kDrive cloud storage service, allowing users to manipulate files and folders remotely. Specifically, for the File resource with the List operation, it lists files contained within a specified folder on a given drive.

Common scenarios where this node is beneficial include:

• Automating file management workflows by retrieving lists of files from specific folders.
• Integrating kDrive file listings into broader automation pipelines, such as syncing files or triggering actions based on file presence.
• Building dashboards or reports that display current folder contents dynamically.

For example, you could use this node to list all files in the root folder of a particular drive to monitor new uploads or changes.

Properties

Output

The output contains a JSON object representing the response from the kDrive API listing the files in the specified folder. This typically includes metadata about each file such as file IDs, names, sizes, types, and other attributes provided by the API.

No binary data is output for the List operation; the output is purely JSON-formatted metadata about the files.

Example output structure (simplified):

{
  "files": [
    {
      "id": "fileId1",
      "name": "example.txt",
      "size": 12345,
      "type": "file",
      ...
    },
    {
      "id": "fileId2",
      "name": "photo.jpg",
      "size": 54321,
      "type": "file",
      ...
    }
  ],
  "limit": 1000,
  "total": 2
}

Dependencies

• Requires an active connection to the kDrive API via an API authentication token.
• The node expects credentials containing an access token and base API URL.
• Network connectivity to https://api.infomaniak.com/2 is necessary.
• No additional external libraries beyond those bundled with n8n are required.

Troubleshooting

• Invalid Drive ID or Parent Folder ID: If these IDs are incorrect or do not exist, the API will return errors or empty results. Verify IDs from your kDrive account.
• Authentication Errors: Ensure the API token credential is valid and has sufficient permissions.
• API Rate Limits or Connectivity Issues: Network problems or rate limiting by kDrive can cause request failures.
• Empty Results: If the folder is empty or the wrong folder ID is used, the result will be an empty file list.
• Error Messages: The node throws detailed errors including HTTP status and response data when requests fail, which helps diagnose issues.

Links and References

• kDrive API Documentation
• n8n Documentation - Creating Custom Nodes