# Vidicore The new VidiCore integration in Helmut4 empowers VidiCore users to automate their Media Management in the Cloud and gives you access to control all API driven processes in the backend to design powerful workflows. The Streamdesigner in Helmut4 provides 28 new dedicated VidiCore nodes. By implementing these nodes in a stream, it is possible to communicate with a native VidiCore system to generate workflows in the context of collections, files, items, libraries and metadata. {% hint style="info" %} Note:\ Every single node requires the URL of the related VidiCore system. For that purpose, it is recommended to define variables and use wildcards for the corresponding fields. To successfully connect to the VidiCore system and get the required token regarding a correct authentication it is also mandatory to use the[ VidiCore Get Token](#vidicore-get-token) node in the beginning of all related VidiCore streams. \ The **relative file path** is not identical to the file's path of the locally mounted remote storage. It is referring to the external drive's perspective and points to a certain location inside that storage. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/streamdesigner/nodes/actions/third-party/vidicore.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.