# VidiCore Import File Into New Item Action

he **VidiCore Import File Into New Item Action** node imports a file into **Vidispine VidiCore** and creates (or reuses) the corresponding VidiCore *file datatype* so the media becomes a managed item in VidiCore.

The node requires the **Storage ID** where the file resides and the **remote relative file path** (including extension) as seen from the storage’s external drive perspective. Optionally, a list of VidiCore metadata field values can be provided to enrich the created item during import.

After a successful import, the **node result contains the VidiCore item ID**.

#### Input Parameters

**URL**\
Base URL of the target VidiCore system.

**Remote Relative File Path**\
Relative path and filename (including extension) from the storage/external drive perspective.\
Example: `someFolder/TestFile0.mp4`

**Storage ID**\
ID of the VidiCore storage on which the file is located (e.g., `VX-5`).

**File ID**\
[ID of the VidiCore file object](https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/third-party/vidispine/vidicore/vidicore-delete-item-action) that should be imported or written (if applicable in your workflow).

**Wait Until File Is CLOSED Before Import**\
If enabled, the node will first set the file state to **CLOSED** and then fill the placeholder/import it.\
This is useful when files may still be growing or being written.

**VidiCore Metadata Field Values (optional)**\
List of metadata key/value pairs to be added to the created item.\
The referenced metadata fields must already exist in VidiCore.

**Use Existing VidiCore File If Present**\
Controls how the node behaves if a VidiCore *file datatype* already exists for the given physical file:

* **Enabled:** Use the existing VidiCore file datatype if present; otherwise create a new one.
* **Disabled:** If the VidiCore file datatype already exists, the node fails.

> Note: The VidiCore “file datatype” is separate from the physical file that was copied to storage and scanned.

**Progress Message / Done Message (optional)**\
Dashboard messages shown during and after processing.

**Timeout**\
Timeout in seconds to wait for the VidiCore job processing the import.\
(Default shown here is **480**; increase for long imports.)

**Async**\
Enable or disable asynchronous execution.

<figure><img src="https://1398472304-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcJYkTyk9qgh7aCR6dHIm%2Fuploads%2FUPwRqzKtxAKElH0xpCGK%2Fimage.png?alt=media&#x26;token=bd0e5391-1129-4d51-9cc6-0999e4e67638" alt="" width="350"><figcaption><p>VidiCore Import File Into New Item Action node</p></figcaption></figure>

#### Output and Wildcards

After successful completion, the node result contains the **VidiCore item ID** and can be accessed via:

* [{stream.last\_result}](https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/wildcards/result-or-return-wildcards-2/stream-last_result)
* [{node.result.?}](https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/wildcards/result-or-return-wildcards-2/node-result)

#### Behavior

* Registers/imports a storage-resident file into VidiCore as a new item
* Optionally applies metadata during import
* Can wait until the file is closed before importing
* Can reuse an existing VidiCore file datatype (optional)
* Designed for long-running imports via timeout and async execution

#### Recommended Usage

VidiCore imports can take longer than typical synchronous stream limits.\
It is recommended to run this node **asynchronously** (for example, in the async branch after a [Split Stream Action](https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/misc-21/split-stream-action)) when imports may take significant time.

#### Typical Use Cases

* ingesting rendered deliverables into VidiCore
* importing files copied to VidiCore storage by Helmut workflows
* attaching standardized metadata at ingest time
* integrating Helmut export pipelines with VidiCore-managed media operations