Skip to main content

robocorp-windows

The robocop-windows package brings a library that can be used for Windows desktop automation.

The basic idea of the library is to enable windows and controls to be found by leveraging "locators" (strings that identify how to reach some window or control), then interacting with such elements.

There are three fundamental abstractions in the library:

  • Desktop: enables finding WindowElements and interacting directly with the desktop, like opening or closing apps. These actions aren't tied to a specific Window or Control.
  • WindowElement: enables finding direct ControlElements and interacting with a specific Window.
  • ControlElement: enables finding child ControlElements and interacting with a specific Control.

Note: The library itself always creates these classes which are not expected to be subclassed or instanced directly.

Usage

robocorp-windows

👉 Check that you have added the dependency in your configuration; this library is not part of the robocorp bundle.

  • conda.yaml for automation Task Packages
  • package.yaml for automation Action Packages
  • requirements.txt, pyproject.toml, setup.py|cfg etc. for the rest

The library concepts revolve around the idea that the window of interest will be initially found using find_window and then, with that window reference, other controls can be queried and interacted with (for clicking, entering text etc.).

Below is an example using the Windows' Calculator app:

from robocorp import windows

# Get the Calculator window.
calc = windows.find_window("name:Calculator")

# Press button "0" (the locator may vary based on the Windows version).
button0 = calc.find("(name:0 or name:num0Button) and type:Button")
button0.click()

# Clear the Calculator (the locator may vary based on the Windows version).
calc.click("id:clearEntryButton or name:Clear")

# Send the keys directly to the Calculator by typing them from the keyboard.
calc.send_keys(keys="96+4=")

Guides

API Reference

Explore our API for extensive documentation.

Changelog

A list of releases and corresponding changes can be found in the changelog.

Release files for robocorp-windows 1.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for robocorp-windows 1.1.2
File Size Uploaded
robocorp_windows-1.1.2.tar.gz 202.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for robocorp-windows 1.1.2
File Interpreter ABI Platform
robocorp_windows-1.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 413.4 kB

Release files / robocorp_windows-1.1.2.tar.gz

Download URL robocorp_windows-1.1.2.tar.gz
Size 202.0 kB
Tags Source
SHA-256 checksum
How to use checksums
c4f69ca768b6098858d377596f34522a7d01bad7e1ac9ccf17fee3bdabc7768a
BLAKE2b-256 checksum
How to use checksums
b23768956e049cfccb70aa6ceeeb524e35b8b9fa3973a34e26a679a58f2dc0bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

Release files / robocorp_windows-1.1.2-py3-none-any.whl

Download URL robocorp_windows-1.1.2-py3-none-any.whl
Size 211.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
431d62a74738bb524c19ceebba52bb73949f039e51119fe7fa68936b24bdea0d
BLAKE2b-256 checksum
How to use checksums
aec45bb5bbf4d8f29c23db546c79e825b9ccda171795e777a940b7342be7bad1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 24, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.1.2 This release

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.4

2 release files

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page