Build an UiPath unattended automation and trigger it remotely via the Orchestrator API
domain: docs.uipath.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Develop and publish the automation process from UiPath Studio to Orchestrator — Studio uploads the NuGet package to the Orchestrator feed and creates or updates a Process.
In Orchestrator, create a Job by navigating to Automation > Jobs and associating the Process with an unattended Robot or a Machine Template with available runtime slots.
Obtain an Orchestrator API access token by authenticating against the identity server endpoint with your client credentials (client ID and client secret configured in Orchestrator), then include the token as a Bearer token in subsequent API calls.
Trigger a job via the REST API: send a POST request to `/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs` with a JSON body specifying the `ReleaseKey` (process identifier), `Strategy` (e.g., `ModernJobsCount`), and `JobsCount`.
Poll the job status via GET `/odata/Jobs({jobId})` and check the `State` field until it reaches `Successful` or `Faulted`, then retrieve output arguments or logs as needed.
Known gotchas
UiPath Orchestrator has both a Cloud and an on-premises edition, and their API base URLs and authentication mechanisms differ. Cloud uses the Automation Cloud identity service for OAuth; on-premises uses a local identity server. Ensure you are reading documentation for the correct deployment type.
Robot sessions for unattended automation must be licensed and connected. If the Robot agent on the target machine is offline or the machine has no available runtime license slots, the job will queue indefinitely rather than failing immediately — check Robot connectivity in the Orchestrator Machines panel.
The `ReleaseKey` required to start a job is a GUID that changes when a process is republished with a new package version if version pinning is not configured. Use the latest release key retrieved dynamically from `/odata/Releases` filtered by process name rather than hardcoding it.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?