Remove a server folder and its contents.
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.
Remove Folder
Section titled “Remove Folder”Remove a server folder and its contents.
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”Create a disposable test folder with one test file. Confirm the resolved target, run Remove Folder on that exact folder, then check that the folder is absent. Use only test data while verifying this action.
Result and runtime limits
Section titled “Result and runtime limits”Removal is recursive and does not go through a desktop Trash. Node.js returns the removed application path and can tolerate an absent target; PHP returns true and errors if the folder is absent. Never use an application root or an unchecked user-supplied path.
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.