File Download — Reference
Send a server file as the HTTP download response.
Send a server file as the HTTP download response.
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 Download
Section titled “File Download”Send a server file as the HTTP download response.
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. |
| File Path | The application-relative path of the server file. This is not the browser’s local file-picker path or an HTTP URL. |
| File Name | The download filename presented to the client. When omitted, the runtime uses the source basename. This does not rename the stored file. |
| 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 file. Call the download endpoint through a normal browser navigation or download action and inspect the response and downloaded filename. Confirm the saved bytes match the source file.
Result and runtime limits
Section titled “Result and runtime limits”The file response replaces ordinary JSON output; the exposed Output Result control does not turn this into a metadata-returning operation. Name is not a JSON wrapper. Node.js sends 404 for an absent target; the installed PHP method exits without the same explicit missing-file response, so check existence first for a consistent not-found contract.
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.