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 Info operation, it retrieves detailed metadata about a specific file or directory within a given drive. This is useful when you need to inspect file attributes such as size, creation date, modification date, permissions, or other metadata before performing further actions like downloads, updates, or conditional workflows.

Practical examples:

  • Automatically fetching file details to verify if a file meets certain criteria (e.g., size or type) before processing.
  • Displaying file metadata in dashboards or reports.
  • Using file info to trigger notifications or downstream automation based on file properties.

Properties

Name Meaning
Drive ID The unique identifier of the drive where the file resides.
File ID The unique identifier of the file or directory whose information you want to retrieve.

Output

The output JSON contains the full metadata object returned by the KDrive API for the specified file or directory. This typically includes attributes such as:

  • File or directory name
  • Size in bytes
  • Creation and modification timestamps
  • File type (file or folder)
  • Permissions and sharing settings
  • Other relevant metadata provided by KDrive

No binary data is output for this operation; the response is purely JSON metadata.

Example output structure (simplified):

{
  "id": "fileId",
  "name": "example.txt",
  "size": 1024,
  "created_at": "2023-01-01T12:00:00Z",
  "modified_at": "2023-01-02T15:30:00Z",
  "type": "file",
  "permissions": { ... }
}

Dependencies

  • Requires an active connection to the KDrive API via an API authentication token.
  • The node expects valid credentials configured in n8n that provide access to the KDrive API.
  • Network connectivity to https://api.infomaniak.com is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired API token leading to authorization errors.
    • Incorrect Drive ID or File ID causing "not found" errors.
    • Network connectivity problems preventing API calls.

  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API token credential is valid and has not expired.
    • 404 Not Found: Verify that the Drive ID and File ID are correct and accessible by the authenticated user.
    • Network errors: Ensure your environment can reach the KDrive API endpoint and no firewall blocks exist.

Links and References

Discussion