Container Input (File)

This node receives resources from an external caller (for example the REST interface) and saves them in the (job's) workflow data area. Using the REST interface this can be achieved by sending a multipart/form-data request.
A configured parameter makes the Container Input (File) visible to the external caller and enables the caller to send a resource to the node.

A default file can be specified which is used when the node is executed without a resource from an external caller. The default file will not be moved or copied. Only the path will be exposed.

This node uses the path flow variable to make the local file available to other nodes. To convert the created path variables to string variables which are required by some nodes that have not been migrated yet you can use the Path to String (Variable) node. For further information about file handling in general see the File Handling Guide.

Options

Parameter name

A name for the input parameter (preferably unique). This name is exposed in the REST interface. It must start with a letter, followed by letters and digits and single minus signs or dashes and must end with a letter.

Append unique ID to parameter name

If checked, the name set above will be amended by the node's ID to guarantee unique parameter names. Usually it's a good idea to have this box not checked and instead make sure to use meaningful and unique names in all container nodes present in a workflow.

Description

The description for the input parameter. It is currently not shown in the API specification of the REST interface.

Variable name

The name of the flow variable that contains the location of the local copy of the resource. Any characters are allowed as long as the name is not empty.

Use a default file

Whether to use the default file given below if no external resource is given. An external resource will always take precedence over a default file. Only the path of a default file will be exposed. A default file must exist. The node will fail to execute if this option is disabled or the default file is invalid and no external resource is available.

Read from

Select a file system which stores the data you want to read. There are four default file system options to choose from:

Local File System: Allows you to select a file from your local system.
Mountpoint: Allows you to read from a mountpoint. When selected, a new drop-down menu appears to choose the mountpoint. Unconnected mountpoints are greyed out but can still be selected (note that browsing is disabled in this case). Go to the KNIME Explorer and connect to the mountpoint to enable browsing. A mountpoint is displayed in red if it was previously selected but is no longer available. You won't be able to save the dialog as long as you don't select a valid i.e. known mountpoint.
Relative to: Allows you to choose whether to resolve the path relative to the current mountpoint, current workflow or the current workflow's data area. When selected a new drop-down menu appears to choose which of the three options to use.
Custom/KNIME URL: Allows to specify a URL (e.g. file://, http:// or knime:// protocol). When selected, a spinner appears that allows you to specify the desired connection and read timeout in milliseconds. In case it takes longer to connect to the host / read the file, the node fails to execute. Browsing is disabled for this option.

File, Folder or URL

Enter a URL when reading from Custom/KNIME URL, otherwise enter a path to a file or folder. The required syntax of a path depends on the chosen file system, such as "C:\path\to\file" (Local File System on Windows) or "/path/to/file" (Local File System on Linux/MacOS and Mountpoint). For file systems connected via input port, the node description of the respective connector node describes the required path format. You can also choose a previously selected file/folder from the drop-down list, or select a location from the "Browse..." dialog. Note that browsing is disabled in some cases:

Custom/KNIME URL: Browsing is always disabled.
Mountpoint: Browsing is disabled if the selected mountpoint isn't connected. Go to the KNIME Explorer and connect to the mountpoint to enable browsing.
File systems provided via input port: Browsing is disabled if the connector node hasn't been executed since the workflow has been opened. (Re)execute the connector node to enable browsing.

The location can be exposed as or automatically set via a path flow variable. This is done additionally to the variable that is exposed via Output variable name.

Input Ports

This node has no input ports

Output Ports

: The local location of the resource as a path flow variable.

Views

This node has no views

Workflows

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

Installation

To use this node in KNIME, install the extension KNIME JSON-Processing from the below update site following our NodePit Product and Node Installation Guide:

v5.9

A zipped version of the software site can be downloaded here.

Plugin provider: KNIME AG, Zurich, Switzerland

Plugin version: 5.9.0.v202511130855

On NodePit since: 2025-12-11

Last update: 2026-01-22

KNIME versions: Since v4.4

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!