Actions178
- Drive Actions
- Drive > Activity Actions
- Drive > Activity > Report Actions
- Drive > Files Actions
- Drive > Files > Action Actions
- Drive > Files > Archive Actions
- Drive > Files > Category Actions
- Drive > Files > Category > Right Actions
- Drive > Files > Dropbox Actions
- Drive > Files > External Import Actions
- Drive > Files > Favorite Actions
- Drive > Files > File/Directory Actions
- Drive > Files > File/Directory > Access Actions
- Drive > Files > File/Directory > Access > Invitation Actions
- Drive > Files > File/Directory > Access > Request Actions
- Drive > Files > File/Directory > Access > Teams Actions
- Drive > Files > File/Directory > Access > Users Actions
- Drive > Files > File/Directory > Comment Actions
- Drive > Files > File/Directory > Upload Actions
- Drive > Files > File/Directory > Upload > Session Actions
- Drive > Files > File/Directory > Version Actions
- Drive > Files > Search Actions
- Drive > Files > Share Link > Archive Actions
- Drive > Files > Share Link > Manage Actions
- Drive > Files > Trash Actions
- Drive > Invitations Actions
- Drive > Settings Actions
- Drive > Statistics Actions
- Drive > Users Actions
- Others Actions
- Users Actions
Drive > Files > File/Directory → Hash
AI-generatedSummary
Hash an Infomaniak Kdrive file
Inputs
- authentication — Authentication method to use for the API request. Defaults to OAuth2 if not specified. Select between OAuth2 and API Key authentication schemes provided by the Infomaniak Kdrive integration. This parameter determines how subsequent API calls (including the hash operation) are authorized and executed against the Infomaniak service. When set to OAuth2, an access token is used; when set to API Key, the provided key is included in request headers or query parameters according to the node's implementation. The default value is 'oauth2'.
- path_drive_id (required) — Unique identifier for the Infomaniak Kdrive where the target file or directory resides. This is a numeric identifier corresponding to the drive instance associated with the authenticated account. Must be provided for the operation to locate the correct storage scope. A value of 0 typically defaults to the user's primary drive, but the node's runtime expects an explicit drive ID when multiple drives are configured or when the operation requires precise scoping.
- path_file_id (required) — Numeric identifier of the specific file or directory within the specified drive to hash. This pinpoints the exact resource whose content hash will be computed. The operation targets the file's content (not metadata alone) to generate a digest. If the identifier refers to a directory, behavior depends on the node's implementation—commonly the hash is computed on a representative file or the directory listing, but without explicit source-level confirmation, only the declared parameter purpose is documented here.
- returnFullResponse — When set to true, the node returns the complete API response payload from Infomaniak, which may include additional metadata, status information, or extended data beyond the computed hash. When false (the default), the node extracts and returns only the hash value or a simplified result shape as determined by the node's internal processing. This flag does not alter the hash computation itself, only the form of the returned output.
Output shape
depends on returnFullResponse setting
If returnFullResponse is false (default), the operation returns a hash digest of the specified file's content. The exact algorithm and format are implementation-specific to the Infomaniak Kdrive node; without source-level visibility into the execute function, the returned type is treated as an opaque hash value. If returnFullResponse is true, the full Infomaniak API response is returned instead, containing the hash alongside other request metadata.
Examples
Example 1: Compute SHA-256 hash of a single file using OAuth2 authentication
authentication: oauth2 (default), path_drive_id: 12345, path_file_id: 67890, returnFullResponse: false
Example 2: Retrieve full API response for debugging or downstream processing
authentication: apiKey, path_drive_id: 12345, path_file_id: 67890, returnFullResponse: true