Master the 3 input drivers: Default (Hardware Events), SendWindowMessages, and Simulate Type/Click.
Traditional / Ad-Hoc Approach
Manual human clicks, brittle unmanaged scripts, zero centralized control, and missing fault tolerance.
Enterprise UiPath Standard
Production-grade execution, dynamic Unified Target selectors, automated retry recovery, and centralized governance.
Input Methods determine how UiPath delivers mouse clicks and keystrokes to target applications. The three classic methods are Default (Hardware), SendWindowMessages, and Simulate. Key Sub-topics Breakdown: • Subtopic 1: 3 Input Drivers: Default (Hardware Events), SendWindowMessages (Win32), and Simulate Type/Click • Subtopic 2: Comparison Matrix: Background execution capability, speed, special hotkey support, and UI compatibility • Subtopic 3: Modern Input Modes: Chromium API, Hardware Events, and Background Simulation In enterprise automation environments, Input Methods guarantees reliable execution within the UiPath ecosystem. Key Sub-topics Breakdown: 1. 3 Input Drivers: Default (Hardware Events), SendWindowMessages (Win32), and Simulate Type/Click 2. Comparison Matrix: Background execution capability, speed, special hotkey support, and UI compatibility 3. Modern Input Modes: Chromium API, Hardware Events, and Background Simulation
Simulate and SendWindowMessages allow robots to run in the background behind locked screens or minimized windows at 10x higher speed.
Default moves the physical mouse cursor. SendWindowMessages dispatches Windows WM_CLICK/WM_CHAR messages. Simulate interacts directly with the application's underlying technology driver (DOM/WPF).
Zero unmanaged credentials, explicit timeout ceilings, and structured audit logging.
This enterprise architecture diagram illustrates the execution lifecycle and component boundaries for Input Methods:
ENTERPRISE AUTOMATION PIPELINE (Input Methods):
┌────────────────────────────────────────────────────────────────────────┐
│ Design & Governance Plane: UiPath Studio & Orchestrator │
│ • Packages (.nupkg) • Modern Folders • Credential Assets / Queues │
└───────────────────────────────────┬────────────────────────────────────┘
▼
┌────────────────────────────────────────────────────────────────────────┐
│ Execution Plane: UiPath Robot (Attended / Unattended Agents) │
│ ┌───────────────────────────────────┐ ┌────────────────────────────┐ │
│ │ UI Automation (Simulate / Chromium)│ │ Data & API Processing │ │
│ │ Unified Target & Object Repo │ │ LINQ / HTTP Web Requests │ │
│ └───────────────────────────────────┘ └────────────────────────────┘ │
└───────────────────────────────────┬────────────────────────────────────┘
▼
┌────────────────────────────────────────────────────────────────────────┐
│ Enterprise Exception Handling & Telemetry Sinks │
│ • REFramework States • Try-Catch / Global Handler • Audit Logs │
└────────────────────────────────────────────────────────────────────────┘At a global enterprise handling over 75,000 monthly transactions, operational teams implemented Input Methods to resolve critical production bottlenecks:
Manual intervention caused processing delays and human error in mission-critical transactions.
Deployed Input Methods with automated retry rules, dynamic error recovery, and end-to-end audit logging.
Eliminated 98% of manual touchpoints, achieved sub-second execution latency, and maintained 99.9% uptime.
Evaluate the trade-offs, performance SLAs, and production constraints when deploying Input Methods: