Start with one useful task

Choose a product task you can judge clearly: a more useful description, a consistent option name or a better search title. Keep the first workflow small enough to understand each result.

Connect your catalog

Create or open your Skuze account and follow the Shopify connection instructions shown in Settings and Onboarding. Synchronize the catalog, then find a product in Products. Check that the source facts and images are suitable for the task.

Skuze-managed AI is available in the standard setup without bringing your own OpenAI API key. Access and model options depend on the account's configuration.

Build in Automations

Create an Automation from a template or start from scratch. Choose its trigger, then add the steps you need. The library contains 22 step types for product content, images, research, blogs, decisions and publishing.

Give each step a concrete instruction. Name the intended output, fields, audience and facts to preserve. The prompt helper can suggest instructions that you can edit before saving. If Copilot access is enabled, you can also review a proposed workflow before applying it.

Understand the first trigger

Product is new or changed selects products that are new to the workflow or whose relevant content changed since a successful run. It is not an instant trigger for every change to stock, price or any Shopify field.

New product and Product updated provide narrower choices. Scheduled content runs without a current product and is intended for supported collection or topic-based content steps.

Inspect a test

Save your draft, select a suitable input and use Test. Shopify writes are simulated, but AI generation and research can still run and use Credits. Inspect the steps, output, source links and any errors. A good test is something you can evaluate, not just a green status.

Choose the real execution

Run now uses the current saved draft and can make real Shopify changes. Scheduled runs use the published workflow version while the Automation is active. Publishing a workflow saves the definition for execution; it is not the same as publishing a product or article.

An approval pauses later steps. It does not reverse changes made earlier. Place the step before the action you want a person to approve.

Follow the result

Open run history to see what completed, waited or failed. Content contains generated images and blog drafts. Reviews → Automation approvals contains waiting decisions. Dashboard and Notifications point to work that needs attention.

Read the execution guide and explore all workflow steps.

Put this into practice in SkuzeCreate account