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. Pattern: ^[a-zA-Z](?:[-_]?[a-zA-Z0-9]+)*(?<![0-9])$
Append unique ID to parameter name: If checked, the name set above will be amended by the node's ID "{Parameter Name}-{Relative node 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 but it's used for example when using this workflow as a tool for an AI Agent or when extracting the workflow summary.
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.
Default file: Select the default file to be used when no external resource is provided. The file must exist and be accessible. The path to this file will be exposed via the output flow variable.

Input Ports

This node has no input ports

Output Ports

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

Popular Predecessors

Popular Successors

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.12

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

Plugin provider: KNIME AG, Zurich, Switzerland

Plugin version: 5.12.0.v202605291551

On NodePit since: 2026-08-08

Last update: 2026-08-20

Tags: Modern UI

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!