Skip to content

File Remove — Reference

Reference · Advanced · Server Connect

Delete one server file.

Delete one server file.

  • A Server Connect action and a dedicated test file/folder that the server process can access. Protect the endpoint before exposing private file operations.

Delete one server file.

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.

Setting Meaning
NameNames 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.
File PathThe application-relative path of the server file. This is not the browser’s local file-picker path or an HTTP URL.
Output ResultIncludes a named returned result in action output when applicable. Default off. Check the operation’s actual return type; Download sends the file response instead.

Create a disposable test file, run File Remove with its exact application-relative path, then check If File Exists. The file should be absent. Test your not-found handling separately.

This permanently removes the file; it does not delete a corresponding database record or provide a Trash recovery step. Both runtimes can fail for a missing file. Use Remove Folder for an intentionally recursive folder operation, not File Remove.

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.

You can configure the path and verify the returned result or file effect without confusing it with a page URL or database update.