Skip to main content
When creating your workflow, on the edit page, you will see a section for Assets, to the right of the code window. It’s here that you will see a button to “Add Asset”. Clicking this button will add a new box for an asset, which includes a dropdown menu for you to select which of your (or your organization’s) assets you wish to have available for this workflow. Each asset is injected into the environment in the /share directory. The path that an asset will specifically be written to will be displayed at the top of the asset’s box. It is generally in the format of /share/asset_<UUID>/<filename>. There will also be a clipboard icon, allowing you to copy the path, for use in your script.

​
Using Assets in Nextflow workflows

Assets are available to use in both shell/Docker and Nextflow workflows. When using an asset in a Nextflow workflow, only the primary Nextflow process (i.e., the script executing your nextflow run command) will have access to the /share directory and your asset. If any child processes require use of the asset, you will need to pass the asset filepath to your Nextflow script as an argument. This will allow Nextflow to distribute your asset to any child processes spawned by the main script. For example: 
nextflow run "${REPOSITORY_DIR}/main.nf" \
  -params-file input_params.json \
  --my_asset_arg /share/asset_<UUID>/<filename> \
  --outdir output-$OCX_ANALYSIS_UUID