FlowBotCommander


FlowBotCommander — Free Download. Visual automation tool

FlowBotCommander is a visual automation tool for Windows that replaces scripting with a node-based editor. Users connect blocks to detect images on screen, click, read values with OCR, wait for changes, branch, and trigger webhooks. Targets are located by image recognition and OCR rather than fixed x/y coordinates, so bots continue working when windows move, resize, or dialogs appear in different positions. Flows run locally on the PC and cover single-player idle games, legacy business software without APIs, monitoring tasks, smoke tests, and relief from repetitive clicking.

★★★★★
5.0(1 ratings)
File size: 139 MB
The latest version of FlowBotCommander is: 1.0.0
Operating system: Windows
Languages: English
Price: $0.00 USD (Freemium product ($9 per month or free version))
  • Visual node editor. The core workspace where automation logic is assembled by dragging modules onto a canvas and connecting them with wires. Each node represents a discrete action such as a mouse click, key press, delay, condition, or loop. Connections define execution order and data flow, allowing complex routines to be built without writing code. The editor supports zooming, panning, node grouping, and colour coding for readability.
  • Template matching with tolerance and preview. Locates a target image on screen by comparing a reference picture against the live display. Tolerance settings control how much colour and brightness variation is accepted, which helps when graphics shift slightly between sessions. A preview mode shows the match score and bounding box before the flow runs, so thresholds can be tuned to avoid false positives or missed detections.
  • Optical character recognition (OCR). Reads text and numbers directly from a screen region and converts them into variables for use in conditions, expressions, or logging. OCR supports multiple languages and can be restricted to a small area to improve accuracy. Recognised values can be compared, stored, sent via webhook, or used to drive branching logic inside a flow.
  • Anchors and relative offsets. Anchors are reference points detected on screen, such as a window corner or a distinctive icon. Once an anchor is found, all subsequent clicks and reads are positioned relative to it. This keeps automation stable when a window is moved or resized, because coordinates are recalculated from the anchor instead of being hard-coded.
  • Variables and expressions. Stores values during a run and allows arithmetic, string operations, and comparisons. Variables can hold numbers read by OCR, counters, timestamps, or text from a file. Expressions combine variables and constants to produce new values, which can be used in conditions, loop limits, or webhook payloads. This gives flows memory and the ability to adapt to changing data.
  • Loops and conditions. Provides control flow inside a flow. Loops repeat a set of nodes a fixed number of times, until a condition becomes true, or while a screen state persists. Conditions branch execution based on variable values, image presence, OCR results, or external signals. Together they allow flows to wait for events, retry actions, and choose different paths without manual intervention.
  • Run other profiles as sub-flows. A profile can call another profile as a reusable subroutine. This lets common sequences, such as logging in or navigating a menu, be maintained in one place and invoked from multiple automations. Sub-flows receive and return variables, making it possible to build modular libraries of automation steps that are easier to test and update.
  • Parallel profile groups. Runs several profiles at the same time as a group. Each profile operates independently, which is suitable for monitoring multiple windows or running separate bots on different game accounts. The group can be started, stopped, and monitored as a single unit, while individual profiles retain their own logs and panic-key behaviour.
  • Scheduler. Starts and stops profiles or profile groups at specified times or intervals. Schedules can be one-off or recurring, and can be tied to system events such as startup or idle time. This removes the need to manually launch automations and allows long-running tasks to fit around other computer usage.
  • Panic key. A global hotkey that immediately halts all running flows and profile groups. It is designed for situations where an automation behaves unexpectedly or a user needs to regain control of the mouse and keyboard at once. The panic key works regardless of which window is active and leaves logs intact for later review.
  • Run history and logs. Records each execution with timestamps, node transitions, variable values, and error messages. Logs can be filtered by profile, severity, or time range, and are stored locally. This helps diagnose why a flow stopped, which image match failed, or what value OCR returned during a particular run.
  • HTTP control API. Allows external programs and AI assistants to start, stop, inspect, and modify flows over a local HTTP interface. Commands can read logs, take screenshots, and pass variables into a running profile. This makes it possible to integrate FlowBotCommander with other tools, build custom dashboards, or let an assistant like Claude Code create and debug bots programmatically.
  • Webhook actions. Sends HTTP requests to external services such as Discord, Telegram, Home Assistant, or n8n. Webhooks can carry text, variable values, or screenshots, enabling alerts when a value changes, a rare event occurs, or a flow finishes. They also allow remote commands to be received, so a phone or chat bot can steer automation on the PC.
  • AI integration. Uses local or self-hosted AI models to recognise screen states that template matching cannot handle, such as menus that look different each time or numbers on busy backgrounds. The AI can classify a situation, read several values in one call, and return a decision that the flow uses to branch. No cloud service or per-call cost is required when a local model is used.
  • Speech-to-text module. Listens to a microphone and converts spoken commands into flow steps. It works with Whisper-compatible services, whether local or self-hosted, and is marked as a beta feature. This provides an alternative input method for starting, stopping, or triggering parts of an automation without touching the keyboard.
  • Reusable modules and sharing. Packages a set of nodes into a single module that can be reused across profiles. Modules can be exported, imported, and shared with other users, allowing a library of proven routines to be built over time. This reduces duplication and makes complex automations easier to maintain.
  • Multi-language interface. Provides the editor and menus in English, German, French, Spanish, and Russian. Interface language is independent of OCR language, so a user can work in one language while reading text from an application in another.
  • Free tier and subscription. The free tier allows 100 runs per day with ads. A monthly or yearly subscription removes ads, lifts the run limit, and unlocks all modules. Pricing is listed on the website, and no account is required beyond downloading the free version.

FlowBotCommander was created by a small development team based in Germany and has been available since the early 2020s. The program is written primarily in C# with .NET on Windows, using a node-graph framework for the visual editor and OpenCV-based routines for image matching. The developers have backgrounds in test automation, game tooling, and desktop software. They built the first version to solve repetitive clicking in single-player idle games and later expanded it into a general-purpose automation environment. The project follows a fair-play policy: it is intended for single-player games and software whose terms allow automation, not for multiplayer, PvP, or anti-cheat protected games. Updates are released regularly, with new modules, AI features, and interface languages added over time.

Alternatives to FlowBotCommander

Latest Programs