lawrence2Q: Can Robomotion automate a Windows Server desktop accounting app once per day?
Hi, I want to confirm if Robomotion fits this use case before purchasing.
Setup: one Windows Server/VM per client, with Robomotion installed on each server. The flow runs unattended once per day.
Flow: files are pulled from FTP by an existing script. Robomotion may need to unzip them, open a Windows desktop accounting app, enter username/password, handle an optional warning popup if it appears, click through the import process, confirm/process the batch, use Print to PDF, save the PDF with a specific filename/location, then email it via SMTP/Outlook or call a webhook/API to send the file.
Can Robomotion reliably automate this type of Windows Server desktop app flow? Does each client server need 1 production robot? Does it support conditional logic, for example “if this warning window appears, click OK, otherwise continue”?
Thank you
Faik_Robomotion
May 8, 2026A: Hello,
Yes, Robomotion can reliably automate this type of unattended Windows Server desktop app flows. RPA is for these kinds of complex inter process or application processes which are not possible with API requests.
Each Windows Server or VM where the desktop accounting app is automated needs one production robot license, and the robot should be installed on that same machine.
Robomotion supports conditional logic, so the flow can handle cases like: if a warning popup appears, click OK; otherwise, continue.
It can also handle file operations, unzipping, desktop app interaction, UI interactions for printing to PDF, saving files, email sending via SMTP/Outlook, and webhook/API calls.
The main requirement for reliability is a Windows Desktop session - which may need to be persistent if Desktop Apps are involved - but we have a solution for that, permissions, screen resolution - if image automation is involved -
Best
Thanks. I saw Robomotion has a VM robot/agent and Windows Automation.
For unattended Windows Server use, can Robomotion create or attach to the desktop session using stored credentials, run the desktop app automation, then disconnect/lock afterward?
Or must the Windows user already be logged in before the scheduled flow starts?
Robomotion does not create or attach to a desktop session using stored Windows credentials via RDP. For unattended Windows Server automation, the robot user must already have an active interactive session. We log in via RDP, then use our Transfer Session node to move the RDP session to the local console session, allowing the robot to continue after RDP is closed.