PowerShell Integration

Fill the PowerShell gap in A360. Execute scripts inline or from .ps1 files, capture output directly, control timeout, and handle errors with precision.

Top Benefits

  • Native PowerShell 5 and 7+ support - no extra runtime needed
  • Separate stdout and stderr capture - errors never silently swallowed
  • Configurable timeout to prevent hung scripts from stalling process
  • ErrorAction control - choose Stop or Continue on a per script scope
  • Pass native A360 variables directly to script via the Arguments field
Product video fallback

Tasks

  • Open a PowerShell session
  • Execute either inline scripts or .ps1 files
  • Capture script output to a variable
  • Close and release session
The PowerShell Integration package brings native PowerShell scripting to Automation Anywhere A360. Following the familiar Open / Run / Close pattern used by the JavaScript package, it lets developers write and execute PowerShell directly from within an automation process — no external tools, no additional runtimes, and no agent configuration required beyond a standard Windows PowerShell installation. Scripts can be written inline using the editor, or loaded from an existing .ps1 file on the agent machine. Variables are passed to scripts via the Arguments field using PowerShell's native parameter syntax, keeping the integration clean and intuitive for developers already familiar with PowerShell. Stdout and stderr are captured on separate threads, ensuring errors are never silently swallowed. The ErrorAction setting gives developers explicit control: Stop mode treats any stderr output as a failure Continue mode logs it to the agent and proceeds. A configurable timeout prevents hung scripts from stalling your process indefinitely, with partial output captured and surfaced in the exception if the process is terminated. A working directory field gives scripts a reliable base path for relative file operations. Additional hardening includes Execution Policy selection at session open time, and automatic detection of JVM vs PowerShell bitness mismatches on the agent machine with a clear warning logged when a mismatch is found. Compatible with Windows PowerShell 5.1 (built into Windows) and PowerShell 7+.

Setup process

Install

Download the Bot and follow the instructions to install it in your AAE Control Room.

Configure

Use the Bot in a bot, configure keys and other credentials the Bot will need (see the ReadMe for details.)

Run

That's it - now the Bot is ready to get going!

Requirements and Inputs

  • Windows 5.1 PowerShell (native) or PowerShell 7+ (separate install)

Customer Reviews

0.0(0 reviews)

No reviews yet.