cicd-integrations
2025.10
true
- Overview
- UiPath CLI
- About UiPath CLI
- Downloading UiPath CLI
- Compatibility matrix
- Running UiPath CLI
- Managing NuGet feeds
- Test Manager Support
- Packing projects into a package
- Signing project packages
- Analyzing a project
- Deploying a package to Orchestrator
- Running a job inside Orchestrator
- Testing a package or running a test set
- Testing multiple packages
- Input parameters JSON format
- Deploying assets to Orchestrator
- Deleting assets from Orchestrator
- Running tasks using JSON configuration
- Restoring automation dependencies
- Troubleshooting UiPath CLI
- Azure DevOps extension
- Jenkins plugin
CI/CD integrations user guide
Last updated Mar 27, 2026
Input Parameters JSON Format
Input Parameters JSON Format
When using the -i or --input_path parameter to pass input arguments to your process or test set, you need to provide a JSON file with the following structure:
[
{
"name": "first",
"type": "System.String, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
"value": "\"parameterValue1\""
},
{
"name": "second",
"type": "System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
"value": "12"
},
{
"name": "third",
"type": "System.Boolean, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
"value": "true"
}
]
[
{
"name": "first",
"type": "System.String, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
"value": "\"parameterValue1\""
},
{
"name": "second",
"type": "System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
"value": "12"
},
{
"name": "third",
"type": "System.Boolean, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
"value": "true"
}
]
Each parameter object must contain:
- name - The parameter name as defined in your workflow
- type - The fully qualified .NET type name including assembly information
- value - The parameter value
Understanding the type field
The type field specifies the .NET data type of the parameter. This is crucial for the CLI to correctly interpret and pass the value to your workflow. The type must be the fully qualified assembly name, which includes:
- The type name (e.g.,
System.String,System.Int32,System.Boolean) - The assembly where the type is defined
- Assembly metadata (version, culture, public key token)
Common examples:
- String:
System.String, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e - Integer:
System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e - Boolean:
System.Boolean, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e
Tip:
To obtain the correct type information for your parameters, you can inspect the workflow's .xaml file or use reflection tools to get the fully qualified type name from your .NET assemblies.