Workflow & Automation · Integration
UiPath
Add UiPath to your product for your customers, and give your AI agents governed access to it.
UiPath automations are organised in Orchestrator, and its nouns are the ones an integration works in: a folder that scopes who can see what, a process published into it, a job that is one run of that process, a queue holding the items robots work through, assets carrying the configuration a run needs, and the Action Center tasks where an automation stops and asks a person to decide. An embedded UiPath integration starts jobs with the arguments your product supplies, pushes queue items, reads job state and output, and surfaces the tasks waiting on a human so somebody can answer them inside your product instead of another console. A job is asynchronous and can sit pending until a robot is free, so treating it as a request that returns a value will fail under load. Folders and tenants differ per customer, and fastn holds those credentials per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own UiPath tenant so your product triggers the automations their team already maintains.
Start a job against a published process with your own arguments, then collect its output when the run completes.
Push items into a queue so work from your product is consumed at the rate that customer's robots can handle.
Surface Action Center tasks in your product so the human decision an automation is waiting on happens where people already are.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which jobs failed and which queue items are still unprocessed for one tenant.
An agent starts an approved process within governed permissions, with the folder and arguments recorded.
An agent explains what an automation is waiting for by reading the task assigned to a person.
Example prompt
Which jobs failed in this folder today, and how many queue items are still waiting to be worked?
Set up UiPath in 4 steps
- 01Enable the UiPath connector in your fastn dashboard.
- 02Have each customer authorise their own tenant and confirm which folders your product may start jobs in.
- 03Map the processes, arguments and queues your product uses, then decide how job outcomes and pending tasks are collected.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the UiPath integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a UiPath integration without building it. Your customers connect their own UiPath account inside your product and work their processes, runs and queues there, with no per-customer code on your side.
- Handle the part that actually costs time: runs are asynchronous and can fail long after they are accepted, so an outcome that never arrives must look different from one that succeeded. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a UiPath update is not your on-call problem.
- One integration serves your product and your agents. The same governed UiPath connection powers in-product features and gives AI agents scoped, audited access, so you start work in the automation platform your customers already run, and get the outcome back without wiring it twice.
Used by these teams
Compare with
Microsoft Power Automate
Pega Platform
Datamatics TruBotOften used alongside
Tools the same teams tend to run next to UiPath, across other categories.
Amazon SES
Resend
Mailgun
PostmarkUiPath integration FAQ
How do I add a UiPath integration to my product?
Enable the UiPath connector in your fastn dashboard, then let each customer authenticate their own UiPath account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no UiPath client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own UiPath account?
Yes. Every connection is scoped to the individual customer, so each authorises their own UiPath account and only ever sees their own processes, runs and queues. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this UiPath integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which jobs failed and which queue items are still unprocessed for one tenant.
Who maintains the UiPath integration?
fastn does. When UiPath changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product start a UiPath run and read its outcome?
Yes. Your product can trigger a process in the customer's own UiPath account, pass it input, and take the result back as an event rather than polling for it.
What happens when a UiPath run is slow or fails?
The failure surfaces with its error rather than as a silent timeout, and the run keeps its own identifier so a retry can be matched to the original. That matters more here than in most integrations, because a run that half-completed is not the same as one that never started.
What can I build with the UiPath integration?
A common starting point: let each customer connect their own UiPath tenant so your product triggers the automations their team already maintains. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the UiPath integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding UiPath does not change your per-connector cost. You can start free with 3 connected accounts.
Add UiPath to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.