Software and API Integration: Nisus Central
Your code does the work.
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 management layer that adds a persistent work queue, human approval, central credentials and monitoring to automations written in Python, .NET and Node.js. The code stays the same; scripts take work from the same queue as RPA robots and are monitored on the same screen.
The need
What is missing when you automate with your own code
Scripts and services are quick to write. Once they run in production, these needs appear:
- A durable work queue with retry and deadline rules
- Getting rid of passwords embedded in code
- Seeing which record failed, and why
- Human approval at critical steps
- Scheduling and a clear "is it running right now?" view
- The same reporting and FTE calculation as your RPA robots
Central does not change your code or limit where it runs or which language it uses. It adds the management layer.
Integration
Connect your code to Central in 4 steps
The path: your code → local bridge on the Central Agent (JSON on the same machine) → Central services. The Agent starts jobs from a command-line template; your code calls business functions through the bridge.
Install the Agent
Install the Nisus Central Agent on the Windows machine that runs the code and enter the robot key.
Define your tool
Add the run command for Python, PowerShell or your own app as a custom tool in the Agent's Tools settings.
Export the functions
The Agent exports all 69 functions as a Postman collection and CSV; the test screen copies a cURL command.
Call them
Your code sends JSON to the bridge on
http://localhost:GetNextPendingTransaction,CompleteTransactionand more.
Nisus Central
What Nisus Central adds to your code
Queues and work distribution
Your code picks work items from Central queues. Status, retry count, deadline and postpone date live in one place.
One screen for every platform
Your code on the same dashboard as UiPath, 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
69 functions in 15 groups
Each function can be switched on or off in the Agent. If a disabled function is called, the bridge says so clearly.
| Capability | Bridge functions |
|---|---|
| Transactions (16) | GetNextPendingTransaction, AddTransaction, BulkAddTransactions, CompleteTransaction, RetryTransaction, ForceRetryTransaction, SearchTransactions, SubmitForApproval |
| Jobs (10) | GetNextPendingJob, StartJob, CompleteJob, CreatePendingJob, IsJobStopped, job data |
| Queues and dispatchers (9) | Queue information; dispatchers for files, email and other sources |
| Assets and credentials (4) | Read values and credentials by id or name |
| Approvals (2) | Search and read approval records |
| Logs and error types (7) | Execution log, job and transaction error types |
| Administration (21) | Machine, process, process group, robot, robot user and tool information |
Comparison
Your own plumbing vs. Central
| Topic | Your own queue and logging | Your code + Central |
|---|---|---|
| Work queue, retries and deadlines | Hand-written | Yes, ready |
| Password management | In code or files | Central credentials |
| Human approval | No | Yes, with identity |
| Error records and screenshots | Hand-written | Yes |
| Scheduling and monitoring | Needs another tool | Yes |
| One view with RPA robots | No | Yes |
| Library required | Your choice | None, plain HTTP JSON |
Example scenario
A production line built in code
The dispatcher and performer structure from UiPath REFramework works the same way in any language. NisusAI's official frameworks provide it as a reference.
- 1
Dispatcher
A script adds records from a file, email or database to the queue with
BulkAddTransactions. - 2
Performer loop
A service takes the next record with
GetNextPendingTransactionand loops until the queue is empty. - 3
Credentials
The target system password is read at run time with
GetCredentialAssetByName. - 4
Result
CompleteTransactionwrites success or failure with a category and screenshot. - 5
Approval
Exceptions go to approval with
SubmitForApproval. - 6
Stop
IsJobStoppedlets the code honour a stop request from Central safely.
Fit
Who is it for?
A good fit
- Teams writing automation in Python, PowerShell or .NET next to RPA tools
- IT teams bringing scripts under enterprise monitoring and audit
- Security teams that want passwords out of code
- Leadership that wants code and robots in one FTE report
Not a fit
- Serverless functions that run only in the cloud, not on a Windows machine
- Small teams with a single automation and no need for queues, approvals or audit
FAQ
Frequently asked questions
How does automation built with Python scripts pass an enterprise audit?
An audit asks three things: who started the job, with what authority it ran and who approved it.Once the script is connected to Central, passwords leave the code, every run is recorded and the approval step is kept with the user's identity.
Which languages can we use?
Any language that can make an HTTP request: Python, PowerShell, C#, Java, Node.js, Go.The bridge speaks plain JSON.
Do we need a token or API key?
No.The bridge only accepts calls from the same machine; it recognises the Windows user, and the Agent handles the secure connection to Central.
Where is the list of functions?
The Agent exports every function as a Postman collection and CSV.The test screen can copy a cURL command.
How does Central start my script?
With the command-line template you define in the Agent's Tools settings.Central starts it on a schedule or on demand and tracks its status.
Are there ready-made examples for a dispatcher and performer in code?
Yes.NisusAI's official frameworks show the dispatcher and performer production-line structure; the same structure works in any language.
Can AI assistants reach Central data over MCP?
The Nisus Central MCP server lets AI assistants read process, robot, transaction and FTE data within each user's permissions.
How does a Python script take work from a queue?
The script sends a GetNextPendingTransaction JSON call to the bridge on the same machine, processes the returned item and writes the result with CompleteTransaction.The loop runs until the queue is empty.
How do we add human approval through the API?
The code sends an item that needs an exception to approval with SubmitForApproval.The decision is recorded with the user's identity; the code reads the approval records from the bridge and carries on.
How is a running script stopped from Central?
The code calls IsJobStopped in its loop.A stop request from Central shows up through this call and the code ends its own loop safely.
Which operating system does the Central Agent run on?
The Central Agent that provides the bridge is installed on a Windows machine.As long as your code runs on that machine, the language does not matter; it does not suit serverless functions that run only in the cloud.
Let's connect your code to Central in a day.
Build the queue, credential and approval flow with one of your own scripts.