Actions are the atomic operations performed during automation. They represent specific tasks like clicking a button, typing text, or finding an image on screen. Actions are organized into processes and executed during state transitions.
Control mouse movement and clicks
Left-click at the target location
Parameters:
Double-click at the target location
Parameters:
Right-click to open context menu
Parameters:
Drag from source to destination
Parameters:
Move mouse without clicking
Parameters:
Press or release mouse button
Parameters:
Scroll mouse wheel
Parameters:
Type text and press keys
Type a text string
Parameters:
Press and release a key
Parameters:
Press or release a specific key
Parameters:
Find and verify visual elements
Locate an image on screen and store its location
Parameters:
Check if an image exists (returns true/false)
Parameters:
Wait for an image to disappear from screen
Parameters:
Navigate states and execute processes
Navigate to a target state using pathfinding
Parameters:
Execute another workflow by ID
Parameters:
Timing and debugging utilities
Pause execution for a specified duration
Parameters:
Capture the current screen
Parameters:
Specifies where the action should be performed
Image matching threshold for visual actions
Number of retry attempts if action fails (default: 3)
Maximum time to wait for action completion (default: 5000)
If true, process continues even if this action fails (default: false)
Wait time before executing action
Wait time after action completes
Offset from target location in pixels
Always use a FIND action before clicking an image target. This ensures the element exists and updates the 'Last Find Result' location.
1. FIND (target: login_button) → 2. CLICK (target: "Last Find Result")
Start with 0.85 and adjust based on results. Lower for elements that change slightly, higher for exact matches.
Use pause_after_end for actions that trigger slow operations (e.g., page loads, animations).
Only use for truly optional actions. Most actions should fail the process if they fail.
Group related actions into named processes for reusability and clarity (e.g., 'login_sequence', 'submit_form').