Automation Anywhere Tutorial: RPA & Types of Bots

โšก ะฃะผะฝะพะต ั€ะตะทัŽะผะต

Automation Anywhere delivers robotic process automation through a Control Room, bot developers, and bot runners. This page explains architecture, bot types, features, and industry use cases, plus how the modern Automation 360 platform differs from the older Enterprise 11 release.

  • ???? ๏ธ Archiั‚ะตะบัั‚ัƒั€ะฐ: Control Room governs users, licenses, and source control, while Bot Creator and Bot Runner machines build and execute automations.
  • ๐Ÿค– Bot types: Task Bots automate rule-based steps, MetaBots supply reusable assets, and IQ Bot reads unstructured documents.
  • ๐ŸŒ ะขะตะบัƒั‰ะธะน ะฒั‹ะฟัƒัะบ: Automation 360 replaced Enterprise 11, moving development into a browser-based Control Room with a lightweight Bot Agent.
  • โš™๏ธ ะะธะทะบะธะน ะบะพะด: Recorders and drag-and-drop actions let analysts build automations without writing traditional application code.
  • ๐Ÿ“Š ะ˜ะทะผะตั€ะตะฝะธะต: Bot Insight dashboards report run status, exceptions, and hours saved for every deployed automation.
  • ๐Ÿ›’ ะŸะพะฒั‚ะพั€ะฝะพะต ะธัะฟะพะปัŒะทะพะฒะฐะฝะธะต: The vendor marketplace, now named Agentic App Store, offers prebuilt bots and packages that shorten delivery time.
  • ???? AI layer: Document Automation and Automation Co-Pilot add machine learning and generative assistance on top of core robotic steps.

Automation Anywhere ะžะฑัƒั‡ะตะฝะธะต

ะงั‚ะพ ั‚ะฐะบะพะต ะะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั?

ะะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั is a technique of performing tasks and processes with minimal human assistance. It is a method of making a device, a process, or a system operate on its own without constant human intervention. Automation is used across industries to operate equipment such as machinery, factory processes, boilers, networks, ships, aircraft, and vehicles.

Automation is normally grouped into four categories, ordered from the narrowest scope to the broadest:

  1. ะ ะตะบะพั€ะดะตั€ั‹ ะผะฐะบั€ะพัะพะฒ โ€“ replay a fixed sequence of keystrokes and mouse clicks.
  2. ะกั€ะตะดัั‚ะฒะฐ ะทะฐะฟะธัะธ ะผะฐะบั€ะพัะพะฒ ะฝะฐ ัƒั€ะพะฒะฝะต ะฟั€ะธะปะพะถะตะฝะธั โ€“ run inside one application, such as a spreadsheet or an ERP client, and understand that applicationโ€™s objects.
  3. ะะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั ะฑะธะทะฝะตั ะฟั€ะพั†ะตััะพะฒ โ€“ re-engineers a workflow at the system level, usually through APIs, queues, and rules engines.
  4. ะ ะพะฑะพั‚ะธะทะธั€ะพะฒะฐะฝะฝะฐั ะฐะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั ะฟั€ะพั†ะตััะพะฒ โ€“ drives the user interface of existing applications the way a person would, with no change to the underlying systems.

ะงั‚ะพ ั‚ะฐะบะพะต RPA?

ะ ะพะฑะพั‚ะธะทะธั€ะพะฒะฐะฝะฝะฐั ะฐะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั ะฟั€ะพั†ะตััะพะฒ (RPA) is software that mimics the actions of a human user. It performs actions on a PC to automate business processes that are highly repetitive and rule-based.

Because RPA works at the presentation layer, it can join together legacy mainframes, desktop applications, and web portals that have no shared API. That is why RPA is often described as the fastest way to automate a process without touching the systems underneath. If you are comparing platforms before committing, the roundup of ั€ะพะฑะพั‚ะธะทะธั€ะพะฒะฐะฝะฝั‹ะต ัั€ะตะดัั‚ะฒะฐ ะฐะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธะธ ั‚ะตั…ะฝะพะปะพะณะธั‡ะตัะบะธั… ะฟั€ะพั†ะตััะพะฒ puts the main vendors side by side.

ะงั‚ะพ ั‚ะฐะบะพะต Automation Anywhere?

Automation Anywhere is one of the leading RPA vendors, offering powerful and user-friendly capabilities for automating complex tasks. It is frequently listed among the technologies that reshaped how enterprises operate. The platform combines conventional RPA with intelligent elements such as natural language understanding and the ability to read unstructured data.

Automation Anywhere allows organisations to automate processes that are currently performed by people. It is a web-based management system that uses a Control Room to schedule and run automated tasks, and it can automate end-to-end business operations for a company.

โš ๏ธ ะŸั€ะตะดัƒะฟั€ะตะถะดะตะฝะธะต: The screenshots and client names in the sections below describe Automation Anywhere ะŸั€ะตะดะฟั€ะธัั‚ะธะต 11ั‡ะตะผ ัั‚ะฐั€ัˆะต Windows client-and-server generation. The current generation is ะะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั 360 (originally released as A2019), which is cloud-native and browser-based. The concepts still map across, but the menus, installers, and some component names have changed. See the version comparison below before you install anything.

Automation Anywhere Enterprise 11 vs Automation 360

Automation Anywhere shipped Enterprise 11 as a Windows desktop product: developers installed a thick client called the Bot Creator, and the Control Room ran on a company server. Automation Anywhere later announced end of maintenance for Enterprise 11 in March 2022 and end of life in March 2023, so new projects are built on Automation 360 instead.

Automation 360 moves the whole development experience into the browser. A small program called the Bot Agent is installed on each Windows device and connects that device to the Control Room; there is no separate desktop editor to license and patch. Several component names changed at the same time.

ะ ะฐะนะพะฝ Enterprise 11 (legacy) Automation 360 (current)
Development client ะฃัั‚ะฐะฝะพะฒะปะตะฝะฝะฐั Windows ะ‘ะพั‚ Creator ะบะปะธะตะฝั‚ Browser-based Control Room editor
ะŸะพะดะบะปัŽั‡ะตะฝะธะต ัƒัั‚ั€ะพะนัั‚ะฒะฐ Full client installed per machine Lightweight Bot Agent per machine
Reusable UI assets MetaBot Designer Packages plus the AISense recorder
ะžะฑั€ะฐะฑะพั‚ะบะฐ ะดะพะบัƒะผะตะฝั‚ะพะฒ IQ-ะฑะพั‚ ะะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั ะดะพะบัƒะผะตะฝั‚ะพะฒ
Prebuilt asset marketplace ะœะฐะณะฐะทะธะฝ ะฑะพั‚ะพะฒ Agentic App Store
ะงะตะปะพะฒะตะบ-ะฒ-ะฟะตั‚ะปั ะžะณั€ะฐะฝะธั‡ะตะฝะฝั‹ะน Automation Co-Pilot

ะžัะพะฑะตะฝะฝะพัั‚ะธ Automation Anywhere

  • Intelligent automation for both business and IT tasks.
  • Recorders capture keyboard strokes and mouse clicks so a working task can be produced in minutes.
  • Scriptless authoring, which means no programming knowledge is required for common actions.
  • Automation of long, multi-application tasks that would otherwise take an analyst hours.
  • Distribution of a single workload across multiple computers for parallel execution.
  • Auto-login, which runs scheduled tasks even when the machine is locked.
  • A Credential Vault that stores passwords centrally, so secrets never sit inside bot code.
  • Analytics through Bot Insight, covering both bot performance and the business data the bot processes.

ะŸะพั‡ะตะผัƒ Automation Anywhere?

Teams choose Automation Anywhere for a mix of speed, reach, and governance rather than for any single feature.

  • No programming knowledge is required for standard work; you record your actions or point and click through action wizards.
  • It removes the human error that creeps into repetitive keying and copying.
  • It increases transaction speed, which saves both time and operating cost.
  • Time to value is short and the approach is non-intrusive, because nothing inside the source systems has to change.
  • It automates data transfers and imports or exports data between files and applications, a point covered more broadly in the ะฃั‡ะตะฑะฝะพะต ะฟะพัะพะฑะธะต ะฟะพ RPA.
  • The same automation scales from a single desktop to a data centre without being rewritten.

The trade-off worth naming is that user-interface automation is brittle by nature. When a screen layout changes, the bot can fail, which is why change management and object calibration matter as much as the initial build.

Automation Anywhere Archiั‚ะตะบัั‚ัƒั€ะฐ

Automation Anywhere architecture has three primary components:

  1. ะšะพะผะฝะฐั‚ะฐ ัƒะฟั€ะฐะฒะปะตะฝะธั
  2. ะ‘ะพั‚ Creator
  3. ะ‘ะพั‚-ะฑะตะณัƒะฝ

The diagram below shows how these three pieces fit together: developers publish bots upward into the Control Room, and the Control Room pushes them down to the runner machines that do the work.

Automation Anywhere Architecture showing Control Room, Bot Creator and Bot Runner

ะšะพะผะฝะฐั‚ะฐ ัƒะฟั€ะฐะฒะปะตะฝะธั

The Control Room is the web-based platform that controls Automation Anywhere. In other words, it is the server that governs the bots.

The Control Room also handles:

  1. ะฃะฟั€ะฐะฒะปะตะฝะธะต ะฟะพะปัŒะทะพะฒะฐั‚ะตะปัะผะธ โ€“ accounts, roles, and permissions.
  2. ะšะพะฝั‚ั€ะพะปัŒ ะธัั‚ะพั‡ะฝะธะบะฐ โ€“ the code for every bot is stored centrally, so it is easy to share across systems and to roll back a bad change.
  3. ะ“ะปะฐะฒะฝะฐั โ€“ complete analytics on bot activity. You can see how many bots ran and how many runs passed or failed.
  4. ะฃะฟั€ะฐะฒะปะตะฝะธะต ะปะธั†ะตะฝะทะธัะผะธ โ€“ the licences you purchase are configured and allocated here.

There are two main licence types in Automation Anywhere:

  1. Dev licence โ€“ lets you create a bot, edit a bot, and run a bot.
  2. Run licence โ€“ lets you run a bot only; you cannot make changes to it.

ะ‘ะพั‚ Creator

Developers use a Bot Creator environment to build bots. Their dev licences are validated against the ones configured in the Control Room. Once authenticated, the code of the bots they create is stored in the Control Room. Different developers may build individual tasks or bots, and those bots can then be combined and executed together.

ะ‘ะพั‚-ะฑะตะณัƒะฝ

The Bot Runner is the machine where a bot actually executes. You can have multiple bots running in parallel on separate runners. Only a Run licence is needed. The bots report their execution logs and pass or fail status back to the Control Room.

ะ”ั€ัƒะณะธะต ะฒะฐะถะฝั‹ะต ะบะพะผะฟะพะฝะตะฝั‚ั‹

ะŸะพะฝะธะผะฐะฝะธะต ะฑะพั‚ะพะฒ โ€“ shows statistics and graphs that let you analyse the performance of every bot in the system. It also estimates the time saved by each automated process.

ะ‘ะพั‚-ั„ะตั€ะผะฐ โ€“ integrated with Automation Anywhere Enterprise, it allows you to provision many bots at once and make them available on a rental basis.

Agentic App Store โ€“ the vendor marketplace, originally launched as Bot Store, where you can download prebuilt bots and packages for common business automations instead of building from scratch.

๐Ÿ’ก ะกะพะฒะตั‚: In Automation 360 the Bot Creator is no longer a separate installed program. You log in to the Control Room in a browser and build there, while the Bot Agent handles the connection to your Windows ั€ะฐะฑะพั‡ะธะน ัั‚ะพะป.

ะ’ะธะดั‹ Automation Anywhere ะŸะพะธัะบะพะฒั‹ะต ัะธัั‚ะตะผั‹

Enterprise 11 grouped its automations into three named bot types, illustrated in the figure below. Task Bots sit at the base, MetaBots supply reusable objects to them, and IQ Bot adds a cognitive layer on top.

ะ’ะธะดั‹ Automation Anywhere Bots: Task Bot, Meta Bot and IQ Bot

ะ‘ะพั‚ั‹ ะทะฐะดะฐั‡

Task Bots automate rule-based, repetitive tasks in areas such as document administration, HR, claims management, and IT services. They are the basic building block of any Automation Anywhere project and deliver the most immediate gains in productivity, error reduction, and cost saving.

ะœะตั‚ะฐ ะ‘ะพั‚ั‹

MetaBots are the reusable automation building blocks of Enterprise 11. They are designed so that when an application changes, you only edit the MetaBot once and every process that calls it picks up the fix. MetaBots are not carried forward into Automation 360; the AISense recorder and reusable packages fill the same role there.

IQ-ะฑะพั‚

IQ Bot is the cognitive component. It learns from the corrections a human makes and applies that learning to the next batch, which lets it pull fields out of semi-structured documents such as invoices and purchase orders. In Automation 360 this capability is delivered through Document Automation.

How to Build Your First Bot in Automation 360

The fastest way to try the platform is the free Community Edition, which gives an individual learner a hosted Control Room without a commercial contract. The broad sequence below applies to any Automation 360 tenant.

  1. Register for a Control Room. Sign up for the Community Edition on the vendor site and confirm your email. You receive a cloud Control Room URL of your own; there is no server to install.
  2. Install the Bot Agent. Log in, open the device registration prompt, and install the small Bot Agent package on your Windows machine. This is the piece that lets a cloud Control Room drive your local desktop, and it replaces the heavyweight client from Enterprise 11.
  3. ะกะพะทะดะฐะนั‚ะต ะฑะพั‚ะฐ. From the Automation menu, create a new Task Bot and give it a meaningful name. The browser-based editor opens with an Actions palette on the left and a canvas in the middle.
  4. Record or drag actions. Use the Recorder to capture a short sequence, then switch to the Actions palette and refine it. Common starting actions are Open Application, Browser, and the Excel or CSV file packages.
  5. ะ”ะพะฑะฐะฒัŒั‚ะต ะฟะตั€ะตะผะตะฝะฝั‹ะต. Replace every hard-coded value with a variable. This single habit is what separates a demo bot from one that survives its first month in production.
  6. Move secrets into the Credential Vault. Never type a password into an action field. Store it as a credential and reference the locker instead.
  7. Handle errors. Wrap risky steps in the Error Handler action so an unexpected pop-up produces a logged message rather than a silent stop.
  8. Run and debug. Run the bot against your registered device, then use the step-through debugger and the audit log to see exactly which action failed and with what value.
  9. Deploy and schedule. Check the bot in, then use the Control Room to schedule it against a Bot Runner device or trigger it from an event.

Expect the first useful bot to take a day, not an hour. Most of that time goes into the unglamorous work in steps five through seven, and skipping it is the single most common reason pilots fail to reach production.

Automation Anywhere vs UiPath vs Blue Prism

Automation Anywhere is usually evaluated alongside two other established platforms. All three cover the same core ground, so the decision tends to turn on hosting model, developer profile, and how much intelligent document work you expect.

ะšั€ะธั‚ะตั€ะธะธ Automation Anywhere UiPath Blue Prism
ะžัะฝะพะฒะฝะพะน ะธะฝั‚ะตั€ั„ะตะนั Browser-based Control Room Windows Studio plus web Orchestrator Windows ะกั‚ัƒะดะธั ะดะธะทะฐะนะฝะฐ
Typical author Business analyst and developer Business analyst and developer Trained RPA developer
ะะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั ั ัƒั‡ะฐัั‚ะธะตะผ ะฟะตั€ัะพะฝะฐะปะฐ Yes, via Automation Co-Pilot Yes, via Assistant Limited, oriented to unattended
Document intelligence ะะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั ะดะพะบัƒะผะตะฝั‚ะพะฒ ะŸะพะฝะธะผะฐะฝะธะต ะดะพะบัƒะผะตะฝั‚ะฐ Decipher and partner tools
Free learning edition ะกะพะพะฑั‰ะตัั‚ะฒะพ ะกะพะพะฑั‰ะตัั‚ะฒะพ Trial and academic programme

If you want the detail behind each column, work through the UiPath ัƒั‡ะตะฑะฝะธะบ ะธ Blue Prism ัƒั‡ะตะฑะฝะธะบ before shortlisting.

ะŸั€ะธะปะพะถะตะฝะธั, ะธัะฟะพะปัŒะทัƒัŽั‰ะธะต Automation Anywhere

Automation Anywhere is deployed across most back-office functions. The table below lists the processes that appear most often in each industry.

ะŸั€ะพะผั‹ัˆะปะตะฝะฝะพัั‚ัŒ ะŸั€ะธะผะตะฝะตะฝะธะต Automation Anywhere
ะคะธะฝะฐะฝัะพะฒั‹ะน ัƒั‡ะตั‚ Invoice processing, reporting, and auditing.
HR Automating tasks in PeopleSoft, sending email notifications, and populating employee records.
Operaั†ะธะธ/ะ˜ะข Creating accounts, software set-up, batch processing, and system integration.
ะ ะฐัะฟั€ะพะดะฐะถะฐ Creating and printing invoices, and adding, modifying, or removing customer data in a CRM.
ะœะฐั€ะบะตั‚ะธะฝะณ ะกะพะทะดะฐะฝะธะต ะพั‚ั‡ะตั‚ะพะฒ ะพ ะปะธะดะพะณะตะฝะตั€ะฐั†ะธะธ ะธ ะผะพะฝะธั‚ะพั€ะธะฝะณ ัะพั†ะธะฐะปัŒะฝั‹ั… ะฝะฐัั‚ั€ะพะตะฝะธะน.
ะŸั€ะพะธะทะฒะพะดัั‚ะฒะพ Inventory management, Excel automation, and ERP integration.
ะŸั€ะฐะฒะธั‚ะตะปัŒัั‚ะฒะพ Verification processes, populating subcontractor forms, and automating daily reports.
ะ—ะดั€ะฐะฒะพะพั…ั€ะฐะฝะตะฝะธะต Patient data migration, reporting for doctors, insurance data automation, claim processing, claim status checks, and patient record storage.
ะŸะพั‚ั€ะตะฑะธั‚ะตะปัŒัะบะธะต ั‚ะพะฒะฐั€ั‹ Order processing, data entry, claims processing, FTP automation, and incentive claim handling.
ะ“ะพัั‚ะธะฝะธั‡ะฝั‹ะน ะฑะธะทะฝะตั Competitor price analysis, guest data processing, data verification, and payment processing.
ะ ะธั‚ะตะนะป Gathering product details from manufacturer sites, updating online inventory, and importing website and email sales.

To take this further, read the ะฃั‡ะตะฑะฝะพะต ะฟะพัะพะฑะธะต ะฟะพ RPA for the wider discipline, compare vendors in the list of ะปัƒั‡ัˆะธะต ะธะฝัั‚ั€ัƒะผะตะฝั‚ั‹ RPA, rehearse for hiring rounds with these Automation Anywhere ะฒะพะฟั€ะพัั‹ ะธะฝั‚ะตั€ะฒัŒัŽ ะธ UiPath ะฒะพะฟั€ะพัั‹ ะธะฝั‚ะตั€ะฒัŒัŽ, and see how bot testing overlaps with ะฐะฒั‚ะพะผะฐั‚ะธะทะฐั†ะธั ั‚ะตัั‚ะธั€ะพะฒะฐะฝะธั ะฟั€ะฐะบั‚ะธะบะฐ.

ะงะฐัั‚ะพ ะทะฐะดะฐะฒะฐะตะผั‹ะต ะฒะพะฟั€ะพัั‹ (FAQ)

No. Recorders and drag-and-drop actions cover most work. However, understanding variables, loops, conditions, and basic Excel or SQL concepts makes a large difference once your automations move beyond simple screen replay into real production workloads.

ะ”ะฐ. Automation Anywhere offers a free Community Edition of Automation 360 aimed at individual learners, students, and very small teams. It provides a hosted Control Room with usage limits and is intended for learning rather than commercial production deployments.

In the Credential Vault, a central encrypted store inside the Control Room. Bots reference a credential by name at run time, so passwords never appear in bot code, in exported files, or in the audit logs that administrators review.

An attended bot runs on a personโ€™s desktop and is triggered by that person, usually to speed up part of a live task. An unattended bot runs on a dedicated machine to a schedule or event trigger, with no one signed in.

Classic RPA follows fixed rules. AI layers such as Document Automation and Automation Co-Pilot let a workflow read messy documents, summarise text, and choose between options, so processes that were previously too variable to automate become feasible with human review.

Unlikely in the near term. AI agents shift the work rather than remove it. Someone still has to define the process, set guardrails, connect systems, handle exceptions, and prove the outcome is auditable, which remains a developer and analyst responsibility.

ะŸะพะดะฒะตะดะตะผ ะธั‚ะพะณ ัั‚ะพะน ะฟัƒะฑะปะธะบะฐั†ะธะธ ัะปะตะดัƒัŽั‰ะธะผ ะพะฑั€ะฐะทะพะผ: