UiPath Python SDK
A Python SDK that enables programmatic interaction with UiPath Cloud Platform services including processes, assets, buckets, context grounding, data services, jobs, and more. The package also features a CLI for creation, packaging, and deployment of automations to UiPath Cloud Platform.
Use the UiPath LangChain SDK to pack and publish LangGraph Agents.
Check out other UiPath Integrations to pack and publish agents built with LlamaIndex, OpenAI Agents, Google ADK, and more.
This quickstart guide walks you through deploying your first agent to UiPath Cloud Platform.
Table of Contents
- Installation
- Configuration
- Basic Usage
- Available Services
- Examples
- Command Line Interface (CLI)
- Project Structure
- Development
Installation
pip install uipath
using uv:
uv add uipath
Configuration
Environment Variables
Create a .env file in your project root with the following variables:
UIPATH_URL=https://cloud.uipath.com/ACCOUNT_NAME/TENANT_NAME
UIPATH_ACCESS_TOKEN=YOUR_TOKEN_HERE
Basic Usage
from uipath.platform import UiPath
# Initialize the SDK
sdk = UiPath()
# Execute a process
job = sdk.processes.invoke(
name="MyProcess",
input_arguments={"param1": "value1", "param2": 42}
)
# Work with assets
asset = sdk.assets.retrieve(name="MyAsset")
Available Services
The SDK provides access to various UiPath services:
-
sdk.processes- Manage and execute UiPath automation processes -
sdk.assets- Work with assets (variables, credentials) stored in UiPath -
sdk.buckets- Manage cloud storage containers for automation files -
sdk.connections- Handle connections to external systems -
sdk.context_grounding- Work with semantic contexts for AI-enabled automation -
sdk.jobs- Monitor and manage automation jobs -
sdk.queues- Work with transaction queues -
sdk.tasks- Work with Action Center -
sdk.api_client- Direct access to the API client for custom requests
Examples
Buckets Service
# Download a file from a bucket
sdk.buckets.download(
bucket_key="my-bucket",
blob_file_path="path/to/file.xlsx",
destination_path="local/path/file.xlsx"
)
Context Grounding Service
# Search for contextual information
results = sdk.context_grounding.search(
name="my-knowledge-index",
query="How do I process an invoice?",
number_of_results=5
)
Command Line Interface (CLI)
The SDK also provides a command-line interface for creating, packaging, and deploying automations:
Authentication
uipath auth
This command opens a browser for authentication and creates/updates your .env file with the proper credentials.
Initialize a Project
uipath init
The uipath.json file should include your entry points in the functions section:
{
"functions": {
"main": "main.py:main"
}
}
Running uipath init will process these function definitions and create the corresponding entry-points.json file needed for deployment.
For more details on the configuration format, see the UiPath configuration specifications.
Debug a Project
uipath run ENTRYPOINT [INPUT]
Executes a Python script with the provided JSON input arguments.
Package a Project
uipath pack
Packages your project into a .nupkg file that can be deployed to UiPath.
Note: Your pyproject.toml must include:
- A description field (avoid characters: &, <, >, ", ', ;)
- Author information
Example:
description = "Your package description"
authors = [{name = "Your Name", email = "your.email@example.com"}]
Publish a Package
uipath publish
Publishes the most recently created package to your UiPath Orchestrator.
Project Structure
To properly use the CLI for packaging and publishing, your project should include:
- A
pyproject.tomlfile with project metadata - A
uipath.jsonfile with your function definitions (e.g.,"functions": {"main": "main.py:main"}) - A
entry-points.jsonfile (generated byuipath init) - A
bindings.jsonfile (generated byuipath init) to configure resource overrides - Any Python files needed for your automation
Development
Tools
Check out uipath-dev - an interactive application for building, testing, and debugging UiPath Python runtimes, agents, and automation scripts.
Contributions
Please read our contribution guidelines before submitting a pull request.
3 maintainers
Release files for uipath 2.14.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| uipath-2.14.10.tar.gz | 4.5 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uipath-2.14.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.0 MB
Release files / uipath-2.14.10.tar.gz
| Download URL | uipath-2.14.10.tar.gz |
|---|---|
| Size | 4.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a06e305a4fbd96e2572019a1420587ff6159d4f9406849f3cc0b6b7d7d08a974
|
|
BLAKE2b-256 checksum How to use checksums |
9985c7de36da4a4f5dbac18c45de2abb481e064d0816debabebcfe31a7ac35b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency logRelease files / uipath-2.14.10-py3-none-any.whl
| Download URL | uipath-2.14.10-py3-none-any.whl |
|---|---|
| Size | 436.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46ae2b9eba102c2b469eed5802de81baa13eb317e34e9418c71c25afeb5c9359
|
|
BLAKE2b-256 checksum How to use checksums |
44a99e81e07ced5f7379f0ef4cea85d2c98054917cce667138d599fb08b90eee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency log
