Automation Anywhere
Developer ToolsDrive Automation Anywhere's Control Room from FlowRunner. Agents deploy TaskBots to Bot Runners, monitor executions to completion, feed work items into WLM queues, and browse the bot repository, bridging enterprise RPA with the rest of your stack.
What This Integration Enables
Companies that invested in Automation Anywhere years ago now own something valuable and awkward: a mature bot estate that does real work and lives in its own world. The Control Room knows everything about the digital workforce and nothing about the systems around it, and the AI-era stack grew up outside its walls. The wrong response is a rip-and-replace project. The right one is connection, and that is what this connector does: FlowRunner drives the Control Room as one execution environment among many, so TaskBots become capabilities that modern, event-driven workflows can invoke, feed, and supervise. - Deploy TaskBots to Bot Runner users or device pools on demand, with runtime input variables and progress callbacks - Feed structured work items into Workload Management queues for asynchronous processing - Monitor deployment activity across the Control Room and poll individual executions to completion - Browse the repository and resolve the file IDs, queue IDs, and user IDs a deployment needs The estate keeps doing what it does well: driving applications that have no API. FlowRunner adds what it never had: awareness of the business events that should start a bot, and a [human-in-the-loop](/concepts/human-in-the-loop) escalation path for the runs that end badly.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The invoice batch that carries its own audit trail
Approved invoices flow from the AP process into a WLM queue via Add Work Item, each one a structured row with priority set. Deploy Bot launches the entry TaskBot against the finance Bot Runners, and Get Execution Detail follows the run to completion. The reconciliation is the point: FlowRunner matches queued items against outcomes, writes the ledger to [Google Sheets](/integrations/google-sheets), and nothing enters the ERP without a corresponding record of when, by which bot, on which device.
The failure watch across the whole workforce
Every few minutes, List Activity sweeps the Control Room filtered to failed and stuck runs. New failures post to [Slack](/integrations/slack) with the bot name, device, and error message pulled from Get Execution Detail, and each one appends to the audit log. The operations team stops discovering overnight failures at 9am, and the monthly reliability review reads from a complete record instead of memory.
Spreadsheets as a front door to the digital workforce
A team maintains its work in [Google Sheets](/integrations/google-sheets): refund requests, account updates, records to verify. A scheduled flow reads new rows and loops Add Work Item to enqueue each into the right WLM queue, where Bot Runners drain them asynchronously. List Work Queues doubles as the backlog auditor, flagging queues whose depth is growing faster than the runners clear them, before the backlog becomes a missed SLA.
Human-in-Loop Highlight
The dangerous moment in any RPA operation is the second deployment. Deploy Bot runs a TaskBot under real Bot Runner user identities against production applications, and when a run fails ambiguously, partway through a batch, with an error message that does not say which items completed, the instinct is to run it again. That is how invoices get paid twice. So FlowRunner never redeploys on its own judgment. When Get Execution Detail returns a failure, the agent assembles the evidence a redeploy decision actually needs: the error, the device, and the WLM queue's per-item statuses from List Queue Items showing exactly which work completed before the stop. The AP lead sees "23 of 40 items reached Successful" and decides: redeploy against the remainder, fix and rerun, or hold. The bot executes at machine speed. The decision that could double-process a financial transaction belongs to the person who would answer for it.
Agent Capabilities
9 actionsDeployment
3- Deploy Bot Deploys and runs a TaskBot on one or more Bot Runner users or device pools, by repository file ID, with optional runtime input variables and a callback URL the Control Room posts progress to. Returns a deployment ID for polling. Requires Run/Deploy privileges, and redeploys sit behind this page's human gate.
- Get Execution Detail Retrieves the full detail of a single execution by deployment ID: current status, the bot and device involved, timing, and any error message. The polling action that follows every run to its outcome.
- List Activity Lists deployment activity across the Control Room, including in-progress, queued, and recently completed runs, filterable by status. The fleet-wide monitoring sweep.
Repository
2- List Folder Contents Lists the bots and files in a specific repository folder with filtering, sorting, and pagination. The browse path to a bot's file ID.
- List Files Searches the entire repository for files and bots matching a filter, across all folders. The lookup when the bot's name is known but its folder is not.
Workload Management
2- List Work Queues Lists the WLM queues in the Control Room with pagination and name filtering. The discovery step before feeding items, and the backlog auditor afterward.
- Add Work Item Adds a work item to a WLM queue with data as key-value pairs matching the queue's configured columns and an optional processing priority. Returns the created item with its ID and status.
Administration
2- List Users Lists Control Room users with IDs, usernames, emails, and roles. The lookup for the Run As User IDs that Deploy Bot requires.
- Get Authentication Token Authenticates with the configured username and API key and returns a JSON Web Token, valid for roughly 20 minutes. Sent automatically on every other operation; called directly only to verify credentials or supply a token to external tooling.
Frequently Asked Questions
What can FlowRunner do with Automation Anywhere?
FlowRunner agents can run Get Authentication Token, Deploy Bot, and List Folder Contents in Automation Anywhere, plus 6 more actions.
Does connecting Automation Anywhere to FlowRunner require OAuth?
No. Automation Anywhere connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Automation Anywhere trigger a FlowRunner workflow automatically?
Automation Anywhere doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Automation Anywhere
$100 in credits. No card required. Connect in minutes.