- 28 May 2025
- Print
- DarkLight
- PDF
Overview
- Updated On 28 May 2025
- Print
- DarkLight
- PDF
The Pipeline Templates available in Dataloop’s Marketplace allow you to quickly deploy pre-built pipelines designed for specific tasks and workflows. These include MLOps pipelines, data engineering ETLs, labeling workflows, workforce management, and more.

To get started:
- Use the filter on the left-hand panel to narrow down templates based on your needs.
- Select a template to view more details, and click Install to begin the installation process.
Save a Pipeline as a Template
You can save your pipeline as a template in the Marketplace, making it accessible to users within the project as well as across the entire organization. Once saved, a preview of the pipeline will be automatically generated and displayed in the right-side panel for quick reference and visualization.
Go to the Pipelines from the left-side navigation panel.
Identify the pipeline and click on the Pipeline Name. The pipeline page is displayed.
Click on the Actions and select Save as new template from the list.
Name: Existing pipeline name will be displayed by default. Make changes if needed.
(Optional) Provide a description for the new pipeline template.
Check the following options, if needed:
- Set DPK variables for solution mapping: Set up your template by defining $var(x) in the pipeline variables (limited to datasets and models). These variables will be applied during the solution installation to assign Model or Dataset IDs in the newly created pipeline. For example, to map a solution: dpk.variables = {"x": dpkA.models.yolo8"}.
- Keep all entity-related fields (recommended for internal projects): Ensure that fields related to entities, such as dataset ID, model ID, recipe ID, etc., are preserved in the template. This is applicable for nodes related to Tasks, Datasets, and Models. It is recommended for templates intended for use within the same project where the entities originate.
- Keep service configuration and init input Values: Include any changes to service settings or initialization input values in the template. If not selected, these changes will not be saved, and the settings will revert to their default values. Note that this option does not cover secrets or integrations.
Click Save. A confirmation message is displayed, and the new template will be available in the Marketplace -> Pipelines tab with a preview on the right-side panel.