uipath-cli
latest
false
UiPath CLI user guide
- Overview
- Get started
- Concepts
- Using UiPath CLI
- How-to guides
- CI/CD recipes
- Command reference
- Overview
- Exit codes
- Global options
- uip codedagent
- uip coder
- uip context-grounding
- uip docsai
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- 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-library-object-repository
- get-object-repository
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-instances
- list-workflow-examples
- pack
- publish
- remote
- restore
- run, debug & execution
- run-file
- search-templates
- start-studio
- stop-execution
- tm
- uia
- uip tasks
- uip traces
- uip traces feedback
- Migration
- Reference & support
Syntax and options for `uip maestro flow publish`, which packs a Flow project and uploads the resulting `.nupkg` directly to Orchestrator packages.
uip maestro flow publish packs a Flow project directory and uploads the resulting .nupkg to Orchestrator packages in one step — a shortcut for uip maestro flow pack followed by a manual upload.
Synopsis
uip maestro flow publish <project-path> [output-path] [-n <name>] [-v <version>] [--feed-id <id> | --folder-key <key> | --folder-path <path>]
uip maestro flow publish <project-path> [output-path] [-n <name>] [-v <version>] [--feed-id <id> | --folder-key <key> | --folder-path <path>]
Honors global options. Exit codes follow the standard contract. Requires uip login.
Arguments
<project-path>(required) — path to the Flow project directory (must containproject.uiprojand at least one.flowfile).[output-path](optional) — directory where the generated.nupkgis written before upload. Defaults to a temp directory (<os-tmpdir>/flow-publish-<timestamp>).
Options
| Option | Default | Description |
|---|---|---|
-n, --name <name> | project folder name | Package name. |
-v, --version <version> | 1.0.0 | Package version. |
--feed-id <feedId> | tenant feed | Target feed ID. Mutually exclusive with --folder-key/--folder-path. |
--folder-key <key> | — | Orchestrator folder key (GUID) whose folder-hierarchy feed to publish into — the CLI resolves the feed ID automatically. Mutually exclusive with --feed-id/--folder-path. |
--folder-path <path> | — | Orchestrator folder path, e.g. Shared/Sub — resolved to a feed ID the same way as --folder-key. Mutually exclusive with --feed-id/--folder-key. |
Examples
# Pack and publish to the tenant feed
uip maestro flow publish ./my-flow-project --version 1.2.0
# Publish into a specific folder's feed
uip maestro flow publish ./my-flow-project --folder-key c3d4e5f6-… --version 1.2.0
# Pack and publish to the tenant feed
uip maestro flow publish ./my-flow-project --version 1.2.0
# Publish into a specific folder's feed
uip maestro flow publish ./my-flow-project --folder-key c3d4e5f6-… --version 1.2.0
Data shape (--output json)
{
"Code": "FlowPublish",
"Data": {
"Package": "my-flow-project@1.2.0",
"PackagePath": "/tmp/flow-publish-1710000000000/my-flow-project.flow.Flow.1.2.0.nupkg",
"Upload": [
{ "key": "my-flow-project.flow.Flow.1.2.0.nupkg", "status": "Created" }
]
}
}
{
"Code": "FlowPublish",
"Data": {
"Package": "my-flow-project@1.2.0",
"PackagePath": "/tmp/flow-publish-1710000000000/my-flow-project.flow.Flow.1.2.0.nupkg",
"Upload": [
{ "key": "my-flow-project.flow.Flow.1.2.0.nupkg", "status": "Created" }
]
}
}
Upload[].status is "Created" the first time a given package version is uploaded, or the feed's own conflict status on a repeat upload of the same name/version.
See also
uip maestro flow pack— pack only, without uploadinguip maestro flow init— scaffold the project firstuip maestro flow process— run the published process- Flow overview