- Overview
- JavaScript functions
- Python functions
- Deploy and run
Python functions reach Orchestrator resources through the UiPath() client. Credentials and resource references are resolved at runtime — no secrets are stored in your code or shipped inside the package.
from uipath.platform import UiPath
sdk = UiPath()
from uipath.platform import UiPath
sdk = UiPath()
Assets
Retrieve a named asset value (for example, an API token or base URL) from a folder:
asset = sdk.assets.retrieve("API_BASE_URL", folder_path="Shared")
asset = sdk.assets.retrieve("API_BASE_URL", folder_path="Shared")
Buckets
Download and upload files from Orchestrator storage buckets:
sdk.buckets.download(
name="Invoices",
blob_file_path="invoice.pdf",
destination_path="/tmp/invoice.pdf",
folder_path="Shared",
)
sdk.buckets.download(
name="Invoices",
blob_file_path="invoice.pdf",
destination_path="/tmp/invoice.pdf",
folder_path="Shared",
)
Connections
Retrieve the metadata of an Integration Service connection by id:
conn = sdk.connections.retrieve("connection-id")
conn = sdk.connections.retrieve("connection-id")
This returns the connection's id, base URI, and folder. It does not call the connector. To invoke a connector operation — the equivalent of a Studio activity such as Get Email By ID — see Call an Integration Service activity.
The connection id is a design-time value declared as a binding, not a function input. See Resource bindings.
Other services
The platform client also exposes queues, jobs, processes, documents, and entities. See the uipath SDK reference for the full surface and method signatures.
Credentials and security
- Secrets live in Orchestrator assets, retrieved at runtime — never hardcode them or commit them to the project.
- A function runs under the identity it is invoked with; folder-level RBAC governs which assets and resources it can read.
- Resource references are declared in
bindings.jsonand remapped to the target tenant's resources at runtime, so one package serves every tenant. - An unmapped binding does not fail the job: the call falls back to the design-time identifier, so a function deployed elsewhere can reach for the original tenant's resource.