ImageActionBot logo ImageActionBot

Windows app guide · Android via USB debugging

How to use ImageActionBot like a power user

You do not need to code. This guide takes you from first install to advanced workflows — template images, Window mode execution, and Android automation via USB debugging — so repetitive work becomes fast and reliable.

Release: 1.0.0 Last updated: 2026-04-27

1) Installation and first launch

  • Download the latest setup file and run the installer.
  • After launch, start with a clean workspace.
  • Keep system scaling at 100% or a predictable zoom level for stable image matching.

Download Latest Setup

2) Build your first reliable workflow

  1. Capture a template image from your target screen.
  2. Define steps: click, type, key, scroll, wait, and conditional action.
  3. Tune execution delay and confidence thresholds.
  4. Run a short test before full production execution.

Tip: Add a verification step between critical actions to reduce failure rates.

2.5) Core product modules in ImageActionBot v1.0

  • Light Edition UI: clean English interface with Excel-style green/white visual hierarchy.
  • Multi-tab projects: keep different automations separated, reducing accidental edits in active jobs.
  • Live preview overlay: monitor running state, status messages, and progress without switching windows.
  • Android + Window execution: use one app for desktop and mobile automation workflows.
  • Workflow stability tools: reliable trigger logic, retries, loop controls, and run-state visibility.
  • Execution focus: trigger logic, step ordering, and retries improve workflow stability.
  • Bundle portability: save/load workflow bundles to move processes between systems quickly.

2.6) IAB workflow bundle file: meaning, uses, and safe adoption

An IAB file is an ImageActionBot workflow bundle package. It stores workflow steps, action settings, and execution structure so the same automation can be exported, shared, and imported on another machine without rebuilding each step manually.

Where IAB bundles help most

  • Team handover: pass mature workflows to operators with less setup time.
  • Backup and recovery: keep portable workflow copies before major changes.
  • Multi-system rollout: deploy a consistent process across many desktops.
  • Faster onboarding: new users start from an existing workflow baseline.

How to use an IAB bundle step by step

  1. Build and test your workflow in a source environment.
  2. Export it as an IAB workflow bundle file.
  3. Transfer the file to the target machine or teammate.
  4. Import the IAB file and verify anchors, target actions, and data mappings.
  5. Run a dry test batch before production execution.

Best-practice checks before production

  • Image matching reliability: tune confidence and offset click for dynamic UI states.
  • Anchor stability: validate action points relative to stable visual anchors.
  • Workflow mapping: ensure step names and target actions match exactly.
  • Document layouts: re-check template alignment if scans/layouts differ per machine.
  • Environment parity: resolution, scaling, and application versions should be comparable.

Tip: use semantic file names like invoice_apr_ops_v3.iab and keep versioned backups before edits.

3) Advanced image automation strategy

Template quality

  • Capture unique UI regions; avoid generic icons.
  • Avoid blurry screenshots; clean PNG anchors work best.
  • Maintain consistent screen resolution across runs.

Click precision

  • Use offset clicks when exact center clicks are not safe.
  • Add pre-checks before sensitive actions to prevent incorrect clicks.

4) Android and cross-app automation

  • Enable Android mode only after device authorization is complete.
  • Validate tap/swipe targets on the real device screen before long runs.
  • Keep one dry-run batch for every target app update.
  • For high-value actions, keep manual confirmation fallback.

4.5) Android USB debugging setup (when mobile controls are not visible)

  1. On Android: enable Developer options.
  2. Enable USB debugging.
  3. Connect phone with a data-capable USB cable.
  4. Accept the phone prompt: Allow USB debugging (authorize this computer).
  5. In ImageActionBot switch to Android mode and verify status/controls.

Quick checks if Android mode is not showing

  • Reconnect cable and unlock phone screen.
  • Disable/re-enable USB debugging once, then reconnect.
  • Remove old USB debugging authorizations and re-allow prompt.
  • Use original/OEM cable where possible (charge-only cables fail).
  • Reopen ImageActionBot after device is authorized.

5) Workflow scaling for repeated tasks

  • Align column names with step names.
  • Use sample rows for a dry run before full batch execution.
  • Maintain error-row logging to simplify reruns.
  • Split long jobs into smaller batches to improve reliability.

6) Troubleshooting and optimization

Issue Likely reason Action
Template not found UI changed or low confidence Recapture template, adjust confidence, verify scale
Wrong click position Anchor mismatch Use stronger anchor and calibrated offset
Android action misses target UI shift or stale anchor Re-capture anchor, retune offset, re-test in Android mode
Slow run speed Excess delays Tune waits per step and keep only required checks

Start automating your daily work today

Convert manual repetitive processes into structured automation and unlock daily productivity gains.

Download ImageActionBot Back to Landing Page