RPA Key Components
An RPA platform is not just one piece of software. It is a set of interconnected components that work together — from building bots to running them at scale. Understanding each component helps you navigate any major RPA tool with confidence.
Diagram: The Three Core Components
┌──────────────────────────────────────────────────────────┐ │ RPA PLATFORM │ │ │ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ │ │ STUDIO │ │ ORCHESTRATOR │ │ ROBOT │ │ │ │ (Builder) │ │ (Manager) │ │ (Runner) │ │ │ │ │ │ │ │ │ │ │ │ Where you │ │ Where you │ │ Where bots │ │ │ │ design and │ │ schedule and │ │ actually │ │ │ │ build the │ │ monitor bots │ │ execute │ │ │ │ workflow │ │ │ │ tasks │ │ │ └──────────────┘ └──────────────┘ └──────────────┘ │ │ │ │ │ │ │ └──────────────────┴──────────────────┘ │ │ All three work together │ └──────────────────────────────────────────────────────────┘
Component 1: Studio (The Bot Builder)
The Studio is the development environment where you design the bot's workflow. It is similar to a flowchart drawing tool — you drag activities from a panel and connect them in a sequence. No deep programming experience is needed for basic workflows.
What You Do in Studio
- Design the step-by-step workflow using drag-and-drop
- Configure activities — such as clicking a button, reading an Excel file, or sending an email
- Set variables to store temporary data (like a customer's name or invoice amount)
- Add decision logic using IF conditions and loops
- Test and debug the workflow before deploying it
Studio Interface Overview
┌─────────────────────────────────────────────────────┐ │ STUDIO WINDOW │ │ ┌──────────────┐ ┌─────────────────┐ ┌────────┐ │ │ │ Activities │ │ Workflow Canvas │ │ Props │ │ │ │ Panel │ │ │ │ Panel │ │ │ │ │ │ [Start] │ │ │ │ │ │ - Click │ │ │ │ │ Set │ │ │ │ - Type Text │ │ [Open Browser] │ │ values │ │ │ │ - Read Cell │ │ │ │ │ for │ │ │ │ - Send Email │ │ [Find Element] │ │ each │ │ │ │ - IF / ELSE │ │ │ │ │ step │ │ │ │ - For Loop │ │ [Type Text] │ │ │ │ │ │ - Write Cell │ │ │ │ │ │ │ │ │ │ │ [Click Button] │ │ │ │ │ │ (drag │ │ │ │ │ │ │ │ │ these to │ │ [End] │ │ │ │ │ │ canvas) │ │ │ │ │ │ │ └──────────────┘ └─────────────────┘ └────────┘ │ └─────────────────────────────────────────────────────┘
Component 2: Orchestrator (The Bot Manager)
The Orchestrator is a web-based control panel where you manage, schedule, and monitor all your bots. Think of it as the "mission control" for your entire RPA operation.
What You Do in Orchestrator
- Schedule bots to run at specific times or on a recurring basis
- Assign bots to specific machines or virtual machines
- Monitor bot activity in real time — see which bot is running what
- View logs to check for errors or completed tasks
- Manage queues — lists of items (like invoices) that bots need to process
- Store credentials securely so bots can log into systems without exposing passwords
Orchestrator Dashboard View
┌─────────────────────────────────────────────────┐ │ ORCHESTRATOR DASHBOARD │ │ │ │ BOTS RUNNING NOW: 3 │ │ ┌────────────────┬──────────┬────────────────┐ │ │ │ Bot Name │ Status │ Machine │ │ │ ├────────────────┼──────────┼────────────────┤ │ │ │ Invoice_Bot_1 │ Running │ VM-Server-01 │ │ │ │ HR_Report_Bot │ Idle │ VM-Server-02 │ │ │ │ Email_Bot │ Running │ VM-Server-03 │ │ │ └────────────────┴──────────┴────────────────┘ │ │ │ │ QUEUE: Invoices to process: 142 items │ │ NEXT SCHEDULED: Payroll_Bot at 6:00 AM │ │ ERRORS TODAY: 2 (click to view logs) │ └─────────────────────────────────────────────────┘
Component 3: Robot (The Bot Runtime)
The Robot is the software agent installed on the machine where the bot actually runs. It receives instructions from the Orchestrator and executes the workflow built in the Studio.
Types of Robot Runtimes
| Robot Type | Mode | Where It Runs |
|---|---|---|
| Attended Robot | Triggered by human | Local workstation |
| Unattended Robot | Triggered by Orchestrator | Server or virtual machine |
| Non-Production Robot | Used for development/testing | Developer's machine |
Supporting Components
Queue (Task List)
A queue is a list of work items stored in the Orchestrator that bots process one by one. Each item in the queue is a unit of work — such as one invoice, one customer record, or one email. Multiple bots can pick items from the same queue simultaneously, speeding up processing.
Queue: "Invoices to Process" ┌────────────────────────────────┐ │ Item 1: Invoice #INV-2001 │ ◀─ Bot A picks this │ Item 2: Invoice #INV-2002 │ ◀─ Bot B picks this │ Item 3: Invoice #INV-2003 │ ◀─ Bot C picks this │ Item 4: Invoice #INV-2004 │ (waiting) │ Item 5: Invoice #INV-2005 │ (waiting) └────────────────────────────────┘
Assets (Secure Configurations)
Assets store values that bots need to use — such as system URLs, usernames, passwords, or thresholds. Instead of hardcoding sensitive values into the workflow, the bot retrieves them from the Orchestrator's secure asset store at runtime.
Credential Store
This is a secure vault where bots store and retrieve login credentials. The credentials are encrypted and never exposed in plain text in the workflow code.
Logs
Every action a bot takes gets logged — the time, the step, the outcome, and any errors. Logs are essential for debugging problems and for audit trails in regulated industries.
How All Components Work Together
Developer builds workflow ──▶ STUDIO
│
▼
Workflow published to ──▶ ORCHESTRATOR
│
▼
Orchestrator schedules and sends job to ──▶ ROBOT (on VM)
│
▼
Robot runs the workflow ──▶ Executes on screen
│
▼
Robot pulls work from ──▶ QUEUE
│
▼
Robot logs every action ──▶ LOGS (stored in Orchestrator)
│
▼
Orchestrator sends alert if error occurs ──▶ EMAIL to admin
Summary
An RPA platform has three core components: Studio (where you build bots), Orchestrator (where you manage and monitor them), and Robot (where they run). Supporting components like Queues, Assets, and Logs make the system scalable, secure, and maintainable. Together, these components turn a single bot workflow into an enterprise-grade automation operation.