Automation Anywhere Integration and Nisus Central
Automation Anywhere runs the bot.
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 a management layer that adds cross-platform work queues, human approval and central credentials to Automation 360 bots. Central is installed on premises, so queue data, approval records and logs stay on the company's servers. Bots stay in Automation Anywhere and are monitored on the same screen as the other robots.
The need
What Automation Anywhere teams need in multi-platform estates
Automation Anywhere is a strong cloud-first platform. When other tools are in use too, these needs come to the front:
- Monitoring Automation Anywhere, UiPath and Blue Prism bots on one screen
- Shared queues and work distribution across platforms
- Approvals and audit trails recorded with user identity
- Process data that stays on-premises
- One FTE report for every platform
- Error records with screenshots and category analysis
Automation Anywhere licensing still applies. Central adds the management layer without changing your bots.
Integration
Connect an Automation Anywhere bot to Central in 4 steps
The path: REST Web Service action in the bot → local bridge on the Central Agent → Central services. The call stays on the machine, and no password is stored in the bot.
Install the Agent
Install the Nisus Central Agent on the machine that runs the bot.
Register the robot
Enter the robot key in the Agent. The platform licence sets the number of concurrent robots.
Add Automation Anywhere to Tools
Define Automation Anywhere in the Agent's Tools settings; Central tracks work through it.
Add the call to the bot
Call the local bridge with a REST Web Service action. The Agent exports functions as a Postman collection.
Nisus Central
What Nisus Central adds to Automation Anywhere
Queues and work distribution
Automation Anywhere picks work items from Central queues. Status, retry count, deadline and postpone date live in one place.
One screen for every platform
Automation Anywhere on the same dashboard as UiPath, Blue Prism, Power Automate, Copilot Studio 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 ready-made functions over REST
The local bridge speaks JSON; each function can be switched on or off in the Agent.
| Capability | In an Automation Anywhere bot |
|---|---|
| Take work from a queue | GetNextPendingTransaction; the JSON response goes into a bot variable |
| Record results | CompleteTransaction with success, error and screenshot |
| Bulk add | BulkAddTransactions from Excel or table data |
| Credentials | GetCredentialAssetByName; passwords are never stored in the bot |
| Human approval | SubmitForApproval adds an approval step |
| Search | SearchTransactions filters by status and date |
Comparison
Automation Anywhere alone vs. Automation Anywhere + Central
| Topic | Automation Anywhere alone | Automation Anywhere + Central |
|---|---|---|
| Bot development and execution | Yes | Yes, stays in Automation Anywhere |
| Work queues | Yes, inside the platform | Yes, shared across platforms |
| One screen with UiPath and Blue Prism | No | Yes |
| Per-user approval record | Limited | Yes, exportable |
| Cross-platform FTE report | No | Yes |
| Process data location | Mostly cloud | On-premises, your own servers |
Example scenario
Order production line
Customer orders are processed on an iterative line shared by Automation Anywhere and other robots.
- 1
Collect
Orders from email or a portal are added to a Central queue.
- 2
Process
The Automation Anywhere bot enters the next order into the ERP.
- 3
Approve
Out-of-policy discounts go to the sales manager for approval.
- 4
Record
The result and any error, with a screenshot, are written to Central.
- 5
Retry
Failed orders are reprocessed by the queue rule.
- 6
Report
Order volume, duration and FTE on the dashboard.
Fit
Who is it for?
A good fit
- Organisations running other RPA tools or AI agents next to Automation Anywhere
- Teams that want to keep process data on-premises
- Finance and sales 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
Automation Anywhere runs in the cloud; how does our process data stay on premises?
Nisus Central is installed on the company's servers.Queue data, approval records, logs and screenshots are kept in Central, which means on premises.
How are Automation Anywhere bots reported together with robots on other platforms?
Because the work of every platform passes through the same queues in Central, volumes, durations and hours saved come together in one report.
Do we need to change our Automation Anywhere bots?
No.Bots stay in Automation Anywhere. You add REST calls for shared queues and approvals.
How does an Automation Anywhere bot connect to Central?
With a REST Web Service action to the local bridge of the Central Agent on the same machine.The Agent handles authentication.
Which functions are ready for Automation Anywhere?
69 functions cover queues, transactions, jobs, assets, credentials, approvals and logs.The Agent exports them as a Postman collection.
How does a shared work queue work for Automation Anywhere bots?
The bot takes the next item from a Central queue with the GetNextPendingTransaction call and writes the result with CompleteTransaction.The queue is shared with UiPath, Blue Prism and Power Automate robots; retry count, deadline and postpone date live in Central.
How do we add human approval to an Automation Anywhere bot?
With the SubmitForApproval call.The bot pauses at the approval step, the decision is recorded with the user's identity and the work resumes where it stopped.
Do Automation Anywhere bots need to hold passwords?
No.Credentials are kept in Central; the bot retrieves the value at run time with the GetCredentialAssetByName call.
Let's connect your Automation Anywhere bots to Central.
See the queue and approval flow with one of your own bots.