File/Folder Statistics — Reference
Read metadata for one server file or directory.
Read metadata for one server file or directory.
Before you begin
Section titled “Before you begin”- A Server Connect action and a dedicated test file/folder that the server process can access. Protect the endpoint before exposing private file operations.
File/Folder Statistics
Section titled “File/Folder Statistics”Read metadata for one server file or directory.
Choose a server path
Section titled “Choose a server path”Use an application-relative path beginning with /. In a standard Node.js project, /public/uploads/example.txt is a server path while /uploads/example.txt is its public URL. PHP paths are relative to the application root determined by its runtime. Verify the active target with the file picker instead of copying a path between server models. Do not accept unrestricted user input as a filesystem path.
Settings
Section titled “Settings”| Setting | Meaning |
|---|---|
| Name | Names the operation’s result for later server steps when it returns one. See the result notes for this operation; not all file actions return the same type. |
| Path | The application-relative server path to the target folder or entry. Use the picker for the active target and verify the resolved location. |
| Folder Size | Choose None, Files or Recursive. Avoid treating None as a sum of contained file bytes. PHP statistics sum direct files or recursive file contents for the selected modes; Node.js uses its own child-stat aggregation. The installed PHP Folder List does not forward this option to each stat call, so use a separate statistics step when you need its calculated folder size. |
| Output | Includes the named metadata result or listing in the action response. Default off. Return only fields the caller is permitted to see. |
Worked example
Section titled “Worked example”Read statistics for a known test file and inspect name, path, type, size and modified time. Read a test folder separately and compare the Folder Size modes before using a size as a content total.
Result and runtime limits
Section titled “Result and runtime limits”Metadata is not the file’s content and does not grant download permission. The Node.js field named created is populated from ctime, which is metadata-change time on common systems rather than a guaranteed original creation time. Treat timestamps and path/url fields according to the target runtime.
Connect files to the application
Section titled “Connect files to the application”A returned path or URL is not an access-control decision. Keep private file reads and writes behind server-side identity and ownership checks, and update any database metadata only after the intended file operation succeeds.
Check your result
Section titled “Check your result”You can configure the path and verify the returned result or file effect without confusing it with a page URL or database update.