> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/nodes/actions/third-party/nachtblau-1/medialoopster-6/medialoopster-create-project-action.md). # Medialoopster Create Project Action The Medialoopster Create Project Action allows you to automatically create a project/collection in medialoopster. For this purpose, the medialoopster API is used to create the corresponding project. During this process, the project/collection ID assigned by medialoopster is written to Helmut4's database and stored as a custom project metadata. This ID can be retrieved by using the wildcard: {[project.custom](/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/wildcards/project-related-wildcards-27/project-custom.md).medialoopster}. Additionally, you can define a folder structure for the catalog, which is created automatically. If the node is used to duplicate a project/collection, you have the option to add the source project name to the “Copy of” field. This instructs medialoopster to create a linked instance of each asset from the source project within the duplicated project. Creating a duplicate requires to use this node within a Duplicate trigger with the wildcard: {[project.source.custom](/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/wildcards/project-related-wildcards-27/project-source-custom.md).medialoopster} You can also choose whether to share the linked assets with the copied project/collection by toggling the appropriate switch. You can also set a deletion or retention date for the project/collection using the wildcard: [{date.increment.days.?}](/helmut4-releases/v4.9.1/helmut4-components/streamdesigner/wildcards/date-and-time-21/date-increment-days.md).

Medialoopster Create Project Action