Playbooks

A playbook is a workflow a merchant keeps in the admin: a name, a description, a status, and a straight list of steps. Each step tells one worker what to do. The steps run in the order shown on the playbook.

Merchants edit playbooks under Playbooks. The same playbooks appear on the Playbooks tab in Work Hub.

Playbook list

Playbooks lists each playbook with its name, description, step count, date, and status. The status filter is Draft, Active, or Archived. The list can be sorted by name, date created, or date modified.

Create playbook asks for a name and a description. The name is required. The new playbook opens as a draft.

The bulk action on this list deletes the selected playbooks. It does not start a run.

Playbook screen

The playbook screen has two areas.

Flow is the list of steps.

The side panel has:

• Status. While the playbook is a draft or active, this is a choice of Draft or Active. An archived playbook shows Archived here, and Revert to draft in the page actions. An active playbook has Archive in the page actions.
• Name
• Description

Save keeps the name, description, status, and steps. Delete removes the playbook.

Steps

Flow numbers the steps from top to bottom. An empty playbook says “This playbook does not have any steps yet” and offers Add the first step. Between two steps, Insert a step here adds a step in that place. Add step adds one at the end.

A step shows its number, title, a short preview of the prompt, and the worker’s name. Click the step to edit it.

The step dialog asks for:

• Title
• Prompt. The help text says this prompt instructs the worker on what to do in this step.
• Worker. This is required. Search the list and select one worker.

The first step cannot be removed. Later steps can be removed from the edit dialog. Tools for the step are the tools checked on that worker’s own screen.

Save on the playbook screen keeps the steps with the name, description, and status.

Starting a run

Saving a playbook keeps the definition. A run starts from the product list, from Automations, or from the calendar. Opening a playbook from the Playbooks tab in Work Hub opens this same screen.

Add on that Work Hub tab opens the Success Agent so the merchant can draft a playbook in chat.

Product list

On the product list, when the assistant feature is available, bulk actions include Run Playbook. The merchant selects products, chooses a playbook under Select Playbook, and starts it. The list contains active playbooks for accounts that can use the Success Agent. At most 50 products can be included. The admin then reports “Playbook started for N product(s)”.

Work Hub automations

On the Automations tab in Work Hub, Add opens a form:

• When is Event or Schedule.
• Event is the store activity, grouped under Orders, Products, Inventory, Customers, Reviews, Discounts, Content, and Theme. Examples include Order created, Product updated, and Customer registered.
• Schedule is a schedule builder. The help text says times follow the merchant timezone in the builder and are stored in UTC.
• Action is Worker or Playbook, then the specific worker or playbook.
• Prompt is shown only for a worker. It is optional. The help text says to tell the worker what to do when the trigger fires, or to leave it empty to send only the event details.

A playbook action runs the steps saved on that playbook.

Work Hub calendar

The calendar can save a dated run titled Run Playbook. The dialog asks for a start, an end, how it repeats (Once, Weekly, Monthly, or Quarterly), and which playbook to run. If the store has no playbooks, the calendar says “Create a playbook first.”

Next steps

• Workers — The helpers a step can call, and the instructions and tools on each one
• Events — Start a playbook from a store event or a schedule in Work Hub
• Inbound MCP Tools — Connect outside services on the Tools screen
• Guidelines — Rules aimed at workers and at the Success Agent
• Success Agent — Merchant chat, including drafting a playbook