UiPath Integration and Nisus Central
UiPath runs the robot.
Central runs the operation.
Nisus Central is an orchestration platform that manages UiPath robots on premises. With the official 67-activity package developed by NisusAI, robots take work from Central queues, ask for human approval, read credentials and record the result. Robots are still built in UiPath Studio, and n8n, Power Automate and other tools are managed from the same screen.
The need
Where UiPath teams hit gaps at enterprise scale
UiPath is a strong build-and-run environment. As robot count and teams grow, these needs come to the front:
- One view of robots and AI agents across different platforms
- Queues and scheduling without growing Orchestrator licence cost
- Data and records that stay fully on-premises
- A clear answer to who approved which invoice or purchase
- Regular FTE and savings reports for management
- Retries, bulk operations and advanced search on queues
UiPath robot and Studio licensing stays with UiPath. Central takes over queues, scheduling, monitoring, approvals and reporting.
Integration
Connect a UiPath robot to Central in 4 steps
The path is simple: Nisus Central activity → local bridge on the Central Agent → Central services. Activities talk to the Central Agent on the same machine; the Agent handles authentication and secure communication.
Install the Agent
Install the Nisus Central Agent desktop app on the machine that runs the robot.
Register the robot
Enter the robot key in the Agent. Your platform licence sets how many robots can connect at the same time.
Add UiPath to Tools
UiPath ships ready in the Agent's Tools settings. Central starts and tracks jobs through it.
Install the package
Add the Nisus.CentralRPA.UiPathPackage package in Studio and place activities inside an Automation Bridge Scope.
Nisus Central
What Nisus Central adds to UiPath
Queues and work distribution
UiPath picks work items from Central queues. Status, retry count, deadline and postpone date live in one place.
One screen for every platform
UiPath on the same dashboard as Blue Prism, Power Automate, Copilot Studio, Automation Anywhere and n8n.
Human approval
The flow pauses at an approval step. The decision is recorded with the user's identity and the work resumes where it stopped.
Central credentials
Usernames and passwords are stored in Central. The flow retrieves them securely at run time.
Error records
Error category, error detail and a screenshot are kept for every run.
Machine monitoring
Online status, CPU, memory and disk usage of every machine, live.
Scheduling
Cron-based schedules, dynamic robot allocation and a concurrent-job limit.
FTE and cost reporting
Hours returned to the business and savings, ready for management.
Ready functions
67 ready-made activities in 18 categories
The package exposes almost every Central business function as a drag-and-drop activity in Studio.
| Capability | In UiPath Studio |
|---|---|
| Take work from a queue | Get Next Pending Transaction, Start/Complete Transaction |
| Add work to a queue | Add Transaction, Bulk Add Transactions, Queue Dispatcher (Excel, email, other) |
| Retries | Retry, Bulk Retry and Force Retry Transaction, which ignores the queue retry limit |
| Search and reporting | Search Transactions: filter by process, status, reference and date; count or DataTable |
| Human approval | Submit For Approval adds an approval step |
| Credentials and assets | Get Asset / Get Credential (by id or name) |
| Jobs and data | Job, Job Data, Transaction Data, error types and logging activities |
| Administration | Robot, machine, process, process group and tool information |
Comparison
UiPath alone vs. UiPath + Nisus Central
| Topic | UiPath alone | UiPath + Central |
|---|---|---|
| Robot development and execution | Yes | Yes, stays in UiPath |
| Queue and transaction management | With Orchestrator | Yes, Central queues |
| Manual retry beyond the queue limit | No | Yes, Force Retry |
| One screen with other platforms | No | Yes |
| Per-user approval record | Needs an add-on | Yes |
| FTE and cost reporting | Needs an add-on | Yes |
| Data location | Cloud or on-premises | On-premises, your own servers |
| What developers need | Orchestrator knowledge | Ready-made activities, no extra code |
Example scenario
Production line: dispatcher and performer
The Nisus Central Transactional Framework brings the REFramework pattern to Central. The process runs iteratively like a factory line: one robot puts work into a queue, others process it in turn.
- 1
Dispatcher
Records from Excel, email or another source are queued with Queue Dispatcher.
- 2
Performer
The robot takes the next item with Get Next Pending Transaction and processes it.
- 3
Result
Complete Transaction records success or failure, with a screenshot.
- 4
Approval
Items that need an exception go to Submit For Approval.
- 5
Retry
Failed items are reprocessed by the queue rule, or with Force Retry when needed.
- 6
Report
Search Transactions and Central dashboards track volume, duration and FTE.
Fit
Who is it for?
A good fit
- UiPath teams with a growing robot count and a cost target
- Organisations running other platforms or AI agents next to UiPath
- Finance, procurement and compliance processes that need approvals and per-user audit
- Banking, insurance and public sector teams whose data must stay on-premises
Not a fit
- Small teams with a single automation and no need for queues, approvals or audit
- Teams that are happy with a single platform and have no on-premises data requirement
FAQ
Frequently asked questions
How are UiPath robots managed on premises?
Nisus Central is installed on the company's own servers and manages the queues, scheduling, approvals and records of UiPath robots from there.Data does not leave the company. Robots are still built in UiPath Studio.
How does a company that uses n8n or Power Automate next to UiPath manage them together?
If each tool stays in its own panel, work, approvals and errors are tracked in three different places.Nisus Central connects every tool to the same queues and the same screen, and management gets a single FTE report.
Do we need to rewrite our UiPath robots?
No.Processes stay in UiPath. Nisus Central activities replace the Orchestrator queue activities; the logic stays the same.
How is the Nisus Central activity package installed?
Add the Nisus.CentralRPA.UiPathPackage package from Manage Packages in UiPath Studio.Activities appear under the Nisus.Central category.
Does Central replace UiPath Orchestrator?
For queues, scheduling, monitoring, credentials and approvals, yes.UiPath robot licensing stays with UiPath.
Do our REFramework projects still work?
Yes.The Nisus Central Transactional Framework uses the REFramework structure with Central queues; dispatcher and performer roles are ready.
Can we reprocess an item that hit the queue retry limit?
Yes.Force Retry Transaction clones the item without checking the limit and can set a new deadline or postpone date.
Can UiPath queues and schedules be managed without Orchestrator?
Yes.Robots take work from Central queues; cron-based schedules, dynamic robot allocation and a concurrent-job limit are set in Central. UiPath robot and Studio licensing stays with UiPath.
How do we add human approval to a UiPath robot?
With the Submit For Approval activity.The flow pauses at the approval step, the decision is recorded with the user's identity and the work resumes where it stopped.
Is Nisus Central an alternative to UiPath or a complement?
It can be either. This page covers keeping your UiPath robots and connecting them to Central. If you are weighing Central instead of Orchestrator, we compare the options on the UiPath Alternative page.
Let's connect your UiPath robots to Central in a day.
See queues, approvals and reporting with your own processes.