Automation & AI
Automation Studio: Workflow → Automation → Task
Build reusable Workflows, reusable execution Automations and Tasks, then run them manually or on a schedule with clear execution evidence.
On this page5
Workflow: what to do
Workflow contains the reusable action steps only. It should describe the sequence itself without permanently binding it to a specific Profile, window policy or schedule.
Automation: where and how to run
- Select one/multiple/all Profiles, Groups, Tags or Ghost Profiles.
- Choose selected/new tab/window and optional window bounds/hide behavior.
- Configure concurrency, timeouts, retries and execution policies.
- Keep Ghost Profiles in the shared Ghost runtime while maintaining isolated partitions.
Task: bind and schedule
Task selects one Workflow and one Automation, then decides whether execution is manual or scheduled. Runtime expands a Task into persisted SubTasks that carry the concrete executable work.
Execution and evidence
- Track per-SubTask state and aggregate Task progress.
- Use retries only for recoverable failures.
- Keep errors, logs, IDs, JSON and evidence copyable.
- Use screenshots or human-in-the-loop intervention when visual confirmation is needed.
History and maintenance
Use execution history to inspect past runs, open details and remove obsolete history records. Keep Workflow, Automation and Task responsibilities separate so changes remain understandable.
Move from the concept to Automation Studio
Use the Automation Studio learning page for the interactive workflow, then return here when you need the architecture reference.