Passive Robot

Description Runs scenarios that never touch a screen. Not every automation clicks through an application: reading e-mails, extracting invoices, running SQL queries, processing CSV files or sending Slack and Teams notifications all work without a remote machine or a browser. The Passive robot runs exactly those scenarios — there is no device to connect to, so it needs no address, credentials or monitor, and it connects instantly.

Settings

Field	Description
Robot type	Set to Passive.
Profile Name	Name under which this configuration is saved for reuse.

There is nothing else to configure. The dialog says so: a passive robot has no screen and no device, and only non-visual commands are available.

Available actions

While a Passive robot is connected, the actions menu offers only actions that do not need a screen:

Menu	Actions
Flow Control	Condition, Assert, Exit, Sleep
Flow Control → Loop	Repeat until, Repeat for each item in, Repeat x times, Stop the loop, Skip to the next iteration
Tools	Create variable, Python Code, Log, Execute SQL
Files → Excel	Load CSV File
Files → PDF	Extract PDF custom, Add Image
AI	AI Read, Process Invoice
Project	Section, Comment, Input Form, Import Scenario
Notification	Add Message, Send As Email, Send Slack Message, Send Teams Message
Email	all e-mail actions

Mouse, keyboard, wait and screen actions, Get, file-system actions, clipboard actions and Prompt Actions are not offered. If a scenario that already contains such an action is run on a Passive robot, that action fails with an error.

What is different in the Editor

• No Robot tab. There is no live view to show, so the Robot tab is hidden for as long as the Passive robot is connected and comes back when you disconnect.
• No Teach robot. Element detection reads the screen, so it stays disabled.
• No AI generation. Add with AI…, Edit selection with AI… and Describe with AI write actions for a screen, so the AI menu shows Connect a robot to use the AI instead. A scenario template section that is not built yet cannot be built either: the run pauses on it with The AI writes sections only for a robot with a device.

Unattended runs

A Passive profile is an ordinary profile. Pin it to a scenario in Scenario Settings → Execution → Profile for scheduled runs, or pass it to aiviro-editor run --profile for a run without the Editor window.

tip

Use a Passive profile for back-office scenarios even on a machine that could run an RDP or Desktop robot: nothing has to be connected or logged in, and the scenario cannot fail because a remote session or a screen was unavailable.