Files actions

Every Files action

• Azure Files: Copy FileStart a server-side (async) file copy: from another file in the same account, or from any URL Azure can reach, including a blob, and optionally wait for it to complete. Handles files of any size, unlike Upload's 256 MB ceiling
• Azure Files: Create DirectoryCreate a directory in a share. Azure has no mkdir -p: every parent must already exist, so nested paths need one call per level: turn on Create Parents to make those calls for you
• Azure Files: Create ShareCreate an SMB file share in the storage account, with an optional size quota and metadata. A share is the mount point: directories and files live inside it
• Azure Files: Delete DirectoryDelete a directory. It must be EMPTY first: unlike deleting a share, this does not cascade, and the service refuses a directory that still has anything in it
• Azure Files: Delete FileDelete a file from a share. The file's directory is left in place
• Azure Files: Delete ShareDelete a file share and EVERYTHING in it: every directory and file, irrecoverably unless the account has share soft-delete enabled. Unlike a directory, a share does not have to be empty first
• Azure Files: Download FileDownload a file (optionally a byte range) to a file reference for downstream nodes. Text-like content up to 1 MB is also returned inline
• Azure Files: Generate SAS LinkCreate a time-limited shared access signature URL for a file or a whole share: hand out downloads or accept uploads without sharing the account key. Signed locally with the account key; no API call is made
• Azure Files: Get Directory PropertiesRead a directory's timestamps, SMB attributes and metadata. Also the cheapest existence check: a missing directory answers ResourceNotFound
• Azure Files: Get File PropertiesRead a file's size, content type, timestamps and metadata without downloading it. Also the cheapest existence check
• Azure Files: Get Share PropertiesRead a share's quota, access tier, lease state and metadata. Returns what the share is CONFIGURED as: for how much of it is actually used, use Get Share Stats
• Azure Files: Get Share StatsRead how many bytes a share actually uses. The quota is what you set; this is what you spent: the number to alert on before a share fills up and writes start failing
• Azure Files: Lease FileTake, swap, or release a write lock on a file. Acquire returns a Lease ID: pass it to the Lease ID field of any Upload/Delete/Set step to write to the locked file; every write WITHOUT it is refused while the lease is held. A file lease is INFINITE: it outlives the flow that took it, so release it. Break ends a lease you do not hold
• Azure Files: List DirectoryList a directory's contents. Unlike blob listing, which fakes hierarchy with name prefixes, this returns REAL entries: each tagged file or directory in the type field
• Azure Files: List File RangesList the byte ranges of a file that have actually been written. Azure Files allocates sparsely, so a file's size and its written content are different questions: this answers the second one
• Azure Files: List SharesList the file shares in the storage account, optionally filtered by a name prefix and enriched with metadata, snapshots, or soft-deleted shares
• Azure Files: Set File MetadataReplace a file's metadata. This is a REPLACE, not a merge: names absent from the object are removed, and an empty object clears the metadata entirely
• Azure Files: Set Share MetadataReplace a share's metadata. This is a REPLACE, not a merge: names absent from the object are removed, and an empty object clears the metadata entirely
• Azure Files: Set Share PropertiesChange a share's size quota or access tier. Both are optional, but at least one must be given: an empty call would silently do nothing
• Azure Files: Upload FileUpload content to a file in a share: inline text, base64, a flo:file reference, or an uploaded asset. Azure Files writes in two steps (allocate, then write the bytes in 4 MiB ranges), which this step does for you. Content is capped at 256 MB

Also in Azure