Skip to main content
Node type: upload_file · Version: 1 · Category: Browser Upload an approved local file. This node is not marked with the catalogue’s generic side-effect flag. That classification is not a guarantee that every configured operation is read-only; review the concrete action and its destination.

​
When to use this node

  • Attach an approved local file to a recorded file input.
  • Pass a trusted path from an earlier download or file node into a web form.

​
Example: Upload a generated report

Record the file input and map Write File’s trusted path into file.
Example settings
This shows the important settings, not a complete exported node. Local paths must be selected, mapped from a trusted path, or covered by the runner’s approved boundary. The locator is shortened for readability; use the recorder to create the complete structured locator bundle.
  1. Record the actual file input or its associated label.
  2. Select a local file or map a trusted path output.
  3. Wait for the page’s upload-complete state before submitting.

​
Configuration

A trusted path output from an earlier node may be mapped after the file has been approved.

​
Workflow JSON

The editor stores this node with the following implemented default configuration:
Default node configuration
Values may be entered literally or mapped from an earlier compatible output when the inspector exposes a mapping control. See Variables and data mapping.

​
Inputs

This node has no typed ports in this direction.

​
Outputs

​
Execution behavior

  • The host validates the file boundary before handing the path to the managed browser.
  • Selecting a file does not necessarily wait for the website’s server-side processing.
  • The editor catalogue declares result (any) for mapping. The execution inspector can contain additional evidence fields; inspect a real result before selecting nested paths from object or any outputs.

​
Common issues

  • A plain path string without trusted provenance may be rejected.
  • Custom drag-and-drop upload widgets may require recording their underlying file input.

​
Where it can run

  • Desktop local runner
  • Paired self-hosted runner
  • Managed browser worker

​
Test and inspect

Use Test node in the editor to preview this step with the current configuration. A full run records resolved inputs, outputs, logs, duration, and any artifacts in the execution inspector. Side-effecting or destructive nodes can require an additional confirmation or approved workflow permission.