Workers

A worker is a background helper for the sales channel the merchant is in. It has a type, a name, a short description, instructions, a skill level, and the tools the merchant has checked for it.

Merchants keep workers under Workers. Work Hub can hand a worker a task. An automation or a calendar run can start one too.

Creating a worker

Create worker opens Choose worker type:

• Executor. Runs tasks on demand. Best for content creation, quick updates, and one-off actions.
• Planner. Identifies important changes and highlights what needs review or action next.
• Analyst. The description says this type runs on a schedule to analyze data and produce reports and insights.

The type is chosen here. The worker screen shows it afterwards. It is not a control you change later.

An automation or a calendar run can still target an executor, a planner, or an analyst. The schedule note on the worker screen points every type at the Work Hub calendar and at Automations.

Worker list

Workers shows the name, type, how many tools are checked, task counts, when the worker was created, and skill level. Filters can narrow the list by type and by skill level. The bulk action deletes the selected workers.

Worker screen

• Name
• Description. At most 160 characters. The hint says this helps pick the right worker for the right task, for example in automations: what it does, when to use it, and what it outputs.
• Instructions. What this worker should do. The help text depends on the type: an executor is told the task, the constraints, and the outcome; a planner is told which changes matter and what to highlight; an analyst is told which data and metrics matter and what kind of report to produce.
• Tools. Search and check the tools this worker may use. The section says “Select the tools available to the Worker.” The tools in the list depend on the worker’s type.
• Schedule. The text on the screen says schedules live on the Work Hub calendar for dated runs, or on Automations for an ongoing cron and for store events.
• About workers, with Generate worker. That opens the Success Agent.
• Skill Level. Simple (cheapest), Standard (recommended), or Advanced (costs more). The label says this affects output quality, speed, and cost. Each choice shows a short description and an AI points cost.
• Success Agent. The checkbox is Allow the Success Agent to use this Worker.
• Access. Shown to the store owner when editing a worker, if the store has other accounts. Who can use this worker? is Everyone or Selected only. Selected only lists those accounts.

Starting a task

The task box in Work Hub has three modes: Analyze, Plan, and Execute. Analyze lines up an analyst, Plan a planner, and Execute an executor. The merchant can pick workers of that type. Leaving the choice on Auto still queues that kind of task.

A finished analyst task offers Create a plan. A finished planner task offers Implement. The dialog asks for a Prompt and a Worker, with Auto as the worker choice. The merchant confirms with Queue task. An executor task stays on its own chat.

Continue with Success Agent copies that chat into the Success Agent.

Work Hub marks a task Pending, Running, Completed, Failed, or Cancelled. A pending task can be cancelled.

An automation aimed at a worker can include an optional prompt. One aimed at a playbook uses the playbook’s steps, and the prompt field stays off that form. The worker screen’s schedule note is the place that points at those screens.

Next steps

• Playbooks — Put workers in a linear list of steps
• Events — Start a worker from a store event or a schedule
• Inbound MCP Tools — Connect outside services the worker can use
• Guidelines — Rules aimed at workers and at the Success Agent