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.

Metadata

Release files for robocorp-windows 2.0.0

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 2.0.0
File Size Uploaded Provenance Actions
robocorp_windows-2.0.0.tar.gz 201.9 kB With provenance Details for robocorp_windows-2.0.0.tar.gz

Built distribution (wheel)

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

Total release size: 413.4 kB

Release files / robocorp_windows-2.0.0.tar.gz

Download URL robocorp_windows-2.0.0.tar.gz
Size 201.9 kB
Tags Source
SHA-256 checksum
How to use checksums
a337976aca14fd04ef6711e325a96f571c7a2587ae9b5a208a087a3b57218baa
BLAKE2b-256 checksum
How to use checksums
66568c542a850c28f3e0f78f88704b4268ac3295988b8023cfc37e2b48f9d485
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 1, 2026.

Transparency log

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

Download URL robocorp_windows-2.0.0-py3-none-any.whl
Size 211.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4b085286426214dae774c719ad4eaeccd735f3c765af51a79612b4c469ed5844
BLAKE2b-256 checksum
How to use checksums
fe7f2f08da46d7775eeea1ea215eb2bc9d755f38071bae2d6c4b1cbc37ce14c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 1, 2026.

Transparency log

Security for robocorp-windows 2.0.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for robocorp_windows-2.0.0.tar.gz

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 Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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