Empty Folder — Reference
Remove the contents of a server folder while leaving the folder available.
Remove the contents of a server folder while leaving the folder available.
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.
Empty Folder
Section titled “Empty Folder”Remove the contents of a server folder while leaving the folder available.
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. |
| Output Result | Includes a named returned result in action output when applicable. Default off. Check the operation’s actual return type; Download sends the file response instead. |
Worked example
Section titled “Worked example”Use a disposable test folder containing files and a nested folder. Run Empty Folder, then check that the parent folder still exists and no test entries remain inside it.
Result and runtime limits
Section titled “Result and runtime limits”This recursively removes contents. Node.js ensures the folder exists and returns its path; PHP requires an existing folder and returns true. It is different from Remove Folder, which also removes the parent folder.
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.