Blue Prism Integration and Nisus Central
Blue Prism runs the digital worker.
Central runs the operation.
Status: The Nisus Central package is in early access. Today the connection is set up through Central Agent's local HTTP interface, and the NisusAI team sets it up with you.
Nisus Central is an on-premises orchestration platform that runs Blue Prism digital workers in the same queues and on the same screen as UiPath, Power Automate and other automation tools. Processes stay in Blue Prism; the shared queue, human approval and a single FTE report come from Central.
The need
Where Blue Prism teams hit gaps in multi-platform estates
Blue Prism is an RPA platform with strong governance. Once other tools arrive, these needs come to the front:
- Monitoring Blue Prism, UiPath and Power Automate robots on one screen
- Shared queues and work distribution across platforms
- Approvals recorded with user identity and an exportable audit trail
- Machine monitoring and capacity visibility
- One FTE and savings report for every platform
- Managing processes without disruption during platform migrations
Blue Prism licensing stays with Blue Prism. Central adds the management layer without changing existing processes.
Integration
Connect Blue Prism to Central in 4 steps
The path: Blue Prism Process → local bridge on the Central Agent → Central services. Starting, status, stopping and log reading are handled by the Agent.
Install the Agent
Install the Nisus Central Agent on the Runtime Resource machine.
Register the robot
Enter the robot key in the Agent. The platform licence sets the number of concurrent robots.
Add Blue Prism to Tools
Blue Prism ships ready in the Agent's Tools settings, with run, status, soft stop, log and publish commands defined.
Add the call to the Process
For queues and credentials, call the Agent's local bridge with a Web API definition or a Code Stage.
Nisus Central
What Nisus Central adds to Blue Prism
Queues and work distribution
Blue Prism picks work items from Central queues. Status, retry count, deadline and postpone date live in one place.
One screen for every platform
Blue Prism on the same dashboard as UiPath, 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
What the Agent and local bridge do
Starting and monitoring come from the Agent's Tools definition; business functions come from the local bridge.
| Capability | In Blue Prism |
|---|---|
| Start and monitor | The Agent starts the process on the Runtime Resource and tracks the session status |
| Soft stop and logs | Stop requests from Central and error detail retrieval |
| Take work from a queue | GetNextPendingTransaction Web API call |
| Record results | CompleteTransaction with success, error and screenshot |
| Credentials | GetCredentialAssetByName; passwords are never stored in the process |
| Human approval | SubmitForApproval adds an approval step |
Comparison
Blue Prism alone vs. Blue Prism + Central
| Topic | Blue Prism alone | Blue Prism + Central |
|---|---|---|
| Process development and execution | Yes | Yes, stays in Blue Prism |
| Work queues | Yes, inside Blue Prism | Yes, shared across platforms |
| One screen with UiPath and Power Automate | No | Yes |
| Per-user approval record | Limited | Yes, exportable |
| Machine monitoring | Limited | Yes |
| Cross-platform FTE report | No | Yes |
| Data location | On-premises | On-premises, your own servers |
Example scenario
A multi-platform production line
A loan application moves along an iterative line shared by Blue Prism, UiPath and Power Automate robots.
- 1
Collect
Applications are added to a Central queue.
- 2
Check
Blue Prism runs the core banking checks.
- 3
Documents
UiPath reads and validates the documents.
- 4
Approve
Applications outside the limit go to the credit team for approval.
- 5
Notify
Power Automate informs the customer.
- 6
Report
Volume, duration, errors and FTE for every platform on one dashboard.
Fit
Who is it for?
A good fit
- Organisations running UiPath, Power Automate or AI agents next to Blue Prism
- Teams that want a smooth platform migration
- Banking and insurance processes that need approvals and audit
- Leadership that wants one FTE report for all automation
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
Can Blue Prism and UiPath take work from the same queue?
Yes.A job in a Central queue is taken by whichever platform's robot is free, and the same job is never given to two robots.
Do we need to change our Blue Prism processes?
No.Processes and Objects stay in Blue Prism. You add local bridge calls for shared queues and approvals.
How does Central start Blue Prism?
Through the ready Blue Prism definition in the Agent's Tools settings.The Agent starts the process on the Runtime Resource, tracks it and stops it when needed.
How do we call the local bridge?
With a Blue Prism Web API definition or a Code Stage.The Agent exports every function as a Postman collection.
Does Central help when moving from Blue Prism to another platform?
Yes.Queues, approvals and reporting stay in Central, so management does not change while processes move between platforms.
Can Blue Prism processes take work from a Central queue?
Yes.The process takes the next item from a Central queue with the GetNextPendingTransaction call and writes the result with CompleteTransaction. The Central queue is shared with UiPath, Power Automate and other platforms.
What does Central add next to Blue Prism Control Room?
It shows Blue Prism on one screen with UiPath, Power Automate and AI agents, and adds a shared cross-platform queue, approvals recorded with identity, machine monitoring and one FTE report for every automation.Process development and execution stay in Blue Prism.
How do we add human approval to a Blue Prism process?
With the SubmitForApproval call.The process pauses at the approval step, the decision is recorded with the user's identity and the work resumes where it stopped.
Let's connect your Blue Prism digital workers to Central.
See queues, approvals and reporting with your own processes.