The best desktop automation bots in one place
Bots that automate repetitive desktop workflows. 0 bots in this category.
Automation listings are the general-purpose end of the catalogue: bots that reproduce a repetitive workflow end to end, in the order a person would perform it. A bot belongs here when the work itself is the point - fill this form, move these records, run this nightly routine. Bots whose centre of gravity is a public website are filed under Scraping, and bots built to report change over time are filed under Monitoring.
Expect a launcher that asks for the few values it needs at start, runs locally on your machine, and leaves its result beside itself. Every listing publishes the fields it prompts for, the datasets and files it writes, the commands its configuration actually uses, and its limits - which applications or sites it touches, whether it needs a browser binary, proxies, a solver key or an AI provider, and whether it handles personal data. Nothing here runs on your behalf inside someone else's infrastructure.
Every listing ships the same four launchers: a Windows .exe and .sh scripts for macOS Apple Silicon, macOS Intel, and Linux, delivered as a single raw file with no archive or extraction step. macOS and Linux need the executable bit restored, and macOS asks you to clear the Gatekeeper quarantine attribute before the first run. Automation that drives visible desktop applications behaves differently per windowing system, so test one attended run before you schedule it.
Bots in this category
No bots in this category yet
Automation bots: frequently asked questions
- What counts as a desktop automation bot?
- A compiled launcher that carries out a sequence of desktop or browser steps on your own machine: open an application, fill a form, move records between two programs, save the result. The workflow definition is published with the listing, so the steps are readable before you run them.
- Do these bots run in the cloud?
- No. A launcher runs locally and writes its output beside itself; nothing is hosted, queued or uploaded on your behalf. The only network calls are the configuration fetch at launch and whatever pages or services the workflow itself visits.
- Can I schedule an automation bot to run unattended?
- Yes. The launcher is an ordinary executable, so any operating-system scheduler can start it: Task Scheduler on Windows, launchd or cron on macOS and Linux. Check first whether the listing prompts for values at start - a prompted field needs either a stored default in the project settings or an attended run.
- How do I know what a bot will do before I run it?
- Three tabs tell you. Input lists every value the bot asks for and where it is set; Output documents each dataset, field and file a finished run produces; Config shows the complete published project configuration, which is the same JSON the launcher fetches at start.
- Why does a category page sometimes show no bots?
- The grid lists published listings only. A category is filed by what the bot does, and nothing is added to a category to make it look busier; when no listing is filed yet the page says so and points you at the rest of the catalogue.