Your first workflow
One window, one action, one verification. Build your first working automation in small, observable steps.
Explore the workspace
Select a group at the top and add a step from the module ribbon. The inspector opens a draft. Save adds it to the flow; closing the inspector cancels the draft. Give steps names that describe their purpose.
First example: type into an application
- In Program and files, browse to the actual local .exe of a text editor.
- Add Window and wait for the correct application window to exist.
- Activate it and click its input area.
- In Keyboard, queue the sample text “Hello, JAQ Macro”.
- Test individual steps, then the selected group. Verify that the text actually appears in the application.
Three execution scopes
An individual step test, the selected group and Full flow have different scopes. Full flow uses the project entry group. Subgroups do not execute automatically merely because they appear underneath another group.
Dry run and logs
Dry run helps inspect the flow without applying real input, program launches or file writes; observation steps may still read the actual environment. Check targets and conditions in the log before a real run. Learn the emergency stop shortcut in Settings.
What to add next
Use Find image to verify readiness instead of increasing fixed delays unnecessarily. Move repeated work into helper groups and design a failure path with Condition.