Automations run focused background inspections and record results that can become scoped engineering work; they do not silently deploy storefront changes.
Use Automations for focused background inspection.
An Automation continues independently of an open agent conversation and records a run. It is suitable for repeatable checks where the expected output is a report or finding set.
Choose theme health, performance, accessibility or conversion friction.
Each template explains the category, inspection scope and expected output. Select the smallest template that matches the operational question you need answered.
Current inspection templates are read-only by design.
The run analyzes and reports. It does not deploy storefront changes. Turn a suitable result into a normal scoped session when implementation is required.
Track active, completed, failed and interrupted runs.
The Automations page separates active work from completed results and attention states. A newly triggered run appears immediately using the run id returned by the backend.
Use the output to decide whether engineering work is justified.
A report should identify evidence and next actions. It does not guarantee a business result and should not become production code without the normal scope, staging, QA and approval workflow.
Automation runs can use Engineering Run capacity.
The current plan and Billing page show available capacity. TaskerArmy reserves sufficient capacity before starting qualifying work and releases or finalizes it according to the run outcome.
Related TaskerArmy pages
Connect the store. Start with evidence.
Connect your store, review the audit and choose the first change you want TaskerArmy to prepare in staging.