File Upload — Reference

Move received multipart file data into a configured server folder.

Before you begin

• An appropriately configured Server Connect action and isolated test inputs.

File Upload

Move received multipart file data into a configured server folder.

Settings

Setting	Meaning
Name	Names the upload metadata result, for example upload_files.
Upload Fields	Select the incoming file field or collection. A single-field selection can return one metadata object; a collection selection returns an array. The choice affects how later Insert or Repeat steps should bind the result.
Path	The application-relative server destination. Choose it explicitly: a public Node.js destination normally begins /public/, while its browser URL omits that part. The runtime defaults differ between Node.js and PHP; do not rely on an omitted path.
Template	Optional filename mask. {name} is the base filename, {ext} includes its leading dot, {guid} creates an identifier and {_n} provides collision numbering. The installed Node.js/PHP helpers differ in how {_n} adds separators. Use the returned path and name rather than predicting them.
Replace Spaces	Replaces whitespace in received filenames with underscores before saving.
Replace Diacritics/Accent	Applies the runtime’s transliteration to accented characters. Check filenames from the languages your application accepts.
Strip All Non ASCII	Removes non-ASCII characters from received filenames. It can remove meaningful characters or produce collisions; it is not content validation.
Overwrite	Allows replacement of an existing destination filename. Default off; collision handling otherwise chooses a unique name.
Create Path	Creates a missing destination directory when enabled. Runtime default on. Server filesystem permissions still apply.
Throw Errors	Requests errors for failed/truncated transfers handled by the module. It does not make a missing file required and does not replace size/type validation.
Output	Includes the named upload metadata in the response. Default off. Only return metadata the caller should receive.

Verification example

Build the single-file form and action from Upload a file to your server. Use a disposable .txt file with the required size/type rules. After submission, compare the returned name and path with the actual saved file. If the output is one object, use upload_files.name; if it is an array, repeat its records or deliberately select the appropriate item.

Behavior and limits

The upload result contains metadata such as name, path, url, type and size; it is not a database insert. A declared MIME type or filename extension is not proof of file contents. Restrict the caller and destination, validate uploads before accepting them, and handle a database failure that occurs after the file has already been stored.

Connect this step to the workflow

Place the check or file operation before the work that depends on it, then verify the final HTTP response and any resulting data or file changes.

Check your result

You can configure this operation and verify both its expected result and its failure boundary.