- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip docsai
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- create-project
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-workflow-examples
- pack
- restore
- run-file
- search-templates
- start-studio
- stop-execution
- uia
- uip traces
- Migration
- Reference & support
Syntax and options for `uip maestro flow pack`, which packages a Flow project directory into a `.nupkg` for Orchestrator publication.
uip maestro flow pack packages a Flow project directory into a .nupkg file ready to publish to Orchestrator.
Synopsis
uip maestro flow pack <projectPath> <outputPath> [-n <name>] [-v <version>]
uip maestro flow pack <projectPath> <outputPath> [-n <name>] [-v <version>]
Honors global options. Exit codes follow the standard contract.
Arguments
<projectPath>(required) — path to the Flow project directory (must containproject.uiprojand at least one.flowfile).<outputPath>(required) — output directory where the.nupkgwill be written. Created if it does not exist.
Options
-n, --name <name>— package name. Defaults to the project folder name.-v, --version <version>— package version. Defaults to1.0.0.
Examples
# Pack with defaults (name = folder, version = 1.0.0)
uip maestro flow pack ./invoice-flow ./dist
# Pack with an explicit version
uip maestro flow pack ./invoice-flow ./dist --version 1.2.0
# Override the package name
uip maestro flow pack ./invoice-flow ./dist --name Invoicing.Flow --version 1.2.0
# Pack with defaults (name = folder, version = 1.0.0)
uip maestro flow pack ./invoice-flow ./dist
# Pack with an explicit version
uip maestro flow pack ./invoice-flow ./dist --version 1.2.0
# Override the package name
uip maestro flow pack ./invoice-flow ./dist --name Invoicing.Flow --version 1.2.0
Data shape (--output json)
{
"Code": "FlowPack",
"Data": {
"Package": "invoice-flow.1.2.0.nupkg",
"Output": "./dist/invoice-flow.1.2.0.nupkg"
}
}
{
"Code": "FlowPack",
"Data": {
"Package": "invoice-flow.1.2.0.nupkg",
"Output": "./dist/invoice-flow.1.2.0.nupkg"
}
}
Known issue — Solution pack
When a Flow project is added to a solution (uip solution project add) and packed with uip solution pack, the resulting .nupkg inside the solution zip can be missing critical files (.bpmn, .flow, entry-points.json, bindings_v2.json).
The root cause is a non-recursive copyFiles() helper in the published @uipath/tool-flow — it silently skips the content/ and flow_files/ subdirectories. uip maestro flow pack uses a recursive copy and is not affected.
Workaround: use uip maestro flow pack directly to produce deployable .nupkg files until the solution pipeline is fixed.
See also
uip maestro flow init— scaffold the project firstuip maestro flow validate— validate before packing- Flow overview