UiPath
Developer ToolsDrive UiPath Orchestrator from your flows: start and stop unattended RPA jobs, feed transactional queues and track item status, and enumerate the processes, robots, assets, and folders in a tenant so FlowRunner can trigger and monitor UiPath automations end to end.
What This Integration Enables
UiPath robots are the hands of automation: they drive the software that has no API, the legacy ERP screen, the terminal application, the portal built in 2009. What robots lack is awareness of the world beyond the screen they are driving. They do not know an order just landed in the storefront, that an AI agent just extracted an invoice, or that a human just approved an exception. This connector gives FlowRunner control of UiPath Orchestrator so that awareness and hands finally connect: flows start and stop unattended jobs, feed transactional queues, track item status, and enumerate everything in the tenant. This is orchestration in the literal sense FlowRunner was built for. The robot executes a process; FlowRunner decides when, with what data, what happens on success, and who hears about failure. - Start unattended jobs by release, targeting modern folders, all robots, or specific robot IDs, with JSON input arguments - Feed queues with business data and unique references, then follow items through New, InProgress, Successful, and Failed - Monitor executions across states and stop runaway jobs gracefully or immediately - Enumerate the processes, robots, assets, queues, and folders of a tenant for auditing and discovery The estate runs at machine speed in both layers. What FlowRunner adds between them is judgment: routing, retries, and the [human-in-the-loop](/concepts/human-in-the-loop) moments where a faulted transaction needs a person, not another attempt.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Legacy ERP entry, fed by modern events
Orders land in the storefront, an AI agent normalizes them, and Add Queue Item files each into the entry queue with the order number as its unique Reference. The robot that types into the legacy ERP drains the queue on its schedule, and FlowRunner polls List Queue Items to reconcile: every order either reached Successful or gets accounted for. Duplicates are structurally impossible, and the reconciliation report writes itself into [Google Sheets](/integrations/google-sheets).
The fault path that pages a person
A monitoring flow sweeps List Jobs for Faulted executions every few minutes. Each fault becomes a [PagerDuty](/integrations/pagerduty) incident carrying the process name, job details, and folder, while a summary posts to [Slack](/integrations/slack). The on-call operator decides between re-running with Start Job and holding for investigation. Overnight faults stop being morning surprises with eight hours of queue backlog behind them.
The estate audit nobody staffs
Quarterly, an agent walks the tenant: List Folders for the organization units, List Processes for what can run, List Robots for what runs it, List Assets for the configuration each folder depends on. The inventory lands as a governance report: processes with no recent executions, robots that stopped reporting, folders accumulating assets nobody remembers. The RPA estate, which grows by accretion in every company that has one, becomes something leadership can actually see.
Human-in-Loop Highlight
Stop Job offers two strategies, and the difference between them is exactly where a human belongs. Soft Stop signals the robot to finish gracefully. Kill terminates immediately, and a killed robot stops mid-transaction: an invoice half-typed into the ERP, a record updated in one system but not its counterpart, a target application left in a state no automation planned for. So when FlowRunner's monitoring flags a job running far past its normal duration, the agent does not kill it. It assembles the picture, how long the job has run, what queue items it holds InProgress, what the process touches, and asks the operator: soft stop and wait, kill and reconcile by hand, or let it run. The person who will clean up a half-completed transaction is the person who decides whether to create one. That decision arrives in Slack with full context in minutes, which is the entire point.
Agent Capabilities
10 actionsJobs
4- List Processes Lists the processes (releases) available to start as jobs, each exposing the ReleaseKey that Start Job requires. Scoped by folder, with OData pagination and a name filter.
- Start Job Starts one or more executions for a process in a folder, using the Modern (Job Count) strategy, All Robots, or Specific Robots with robot IDs. Accepts input arguments as a JSON object matching the process parameters. Returns jobs in Pending state for polling.
- List Jobs Lists job executions with their current state: Pending, Running, Successful, Faulted, Stopped, and more. Filterable by state and process name. The polling and monitoring backbone.
- Stop Job Stops or kills a running job by numeric ID. Soft requests a graceful stop; Kill terminates immediately. The Kill path sits behind this page's human gate.
Queues
3- List Queues Lists the transactional queue definitions in a folder, each exposing the Name that Add Queue Item requires.
- Add Queue Item Adds a transaction to a queue with business data as a JSON SpecificContent object, an optional priority, and an optional unique Reference for deduplication when the queue enforces unique references.
- List Queue Items Lists transaction items across a folder's queues with their status: New, InProgress, Successful, Failed. The reconciliation action that proves every fed item reached an outcome.
Tenant
3- List Assets Lists the shared configuration values in a folder: text, integers, booleans, and credential entries, though credential values are never returned. Used for dependency audits.
- List Robots Lists the robots registered in Orchestrator with name, type, and associated machine, scoped by folder.
- List Folders Lists the tenant's folders (Organization Units), each exposing the numeric ID that scopes jobs, queues, assets, and robots. The starting point for every other operation.
Frequently Asked Questions
What can FlowRunner do with UiPath?
FlowRunner agents can run List Processes, Start Job, and List Jobs in UiPath, plus 7 more actions.
Does connecting UiPath to FlowRunner require OAuth?
Yes. UiPath connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can UiPath trigger a FlowRunner workflow automatically?
UiPath doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with UiPath
$100 in credits. No card required. Connect in minutes.