Automation

An automation runs one or more AI actions automatically whenever a chosen event happens — for example, fill in the SEO fields every time a product is created. You decide which event triggers it, which records it applies to, and whether each action’s result is applied automatically or left as a suggestion to review.

Where to find it

Go to Catalogues → AI Assistant, then open Automations from the dashboard Quick start. The list shows each automation’s Name, Trigger event, number of Actions, and whether it is Active.

Creating an automation

1. Click Create automation.
2. In the General section, set a Name, an optional Description, and the Active toggle. Inactive automations are skipped when the event fires.
3. In the Trigger section:
   • Trigger event — one of:
     • Product saved (created or edited) — fires on every product save, whether new or existing.
     • Product created — fires only when a brand-new product is created.
     • Product edited — fires only when an existing product is changed.
     • Image added to product — fires when a new image is added to a product. Paired with an Edit images with AI action, it edits just the newly added image.
   • Priority — higher numbers run before lower ones when several automations match the same event.
   • Optional rule — restrict the automation to records matching a Shopware Rule Builder rule. Leave empty to run on every matching event.
4. In the Actions section, click Add action and pick an action type, then configure it. Available actions:
   • Generate content, Translate content, Improve content, Unify formatting
   • Field mapping (AI extract), Generate from URL
   • Generate SEO, Suggest categories, Suggest search keywords
   • Image Finder, Edit images with AI
5. For each action, set Auto-apply on or Auto-apply off (see below). Add as many actions as you need; they run in order.
6. Click Save.

Auto-apply vs review

Each action carries its own auto-apply switch:

• Auto-apply on — the action’s result is written to the record automatically, with no manual step.
• Auto-apply off — the action produces suggestions instead. Review and apply them like any other job; see Batch jobs.

How chained actions depend on each other

When an automation has several actions, some later actions wait for earlier ones before they run, so they never work on text you haven’t approved:

• A Translate content action waits until the text it will translate is final. If an earlier action produced that text with Auto-apply off, translation stays on hold until you review and accept it.
• Generate SEO and the Extract measures / Extract properties actions wait until the product description they read from is in place from the earlier steps.
• If an Edit images with AI action files images under a manufacturer folder and an earlier action proposed a new manufacturer, the image step waits until you accept that manufacturer suggestion — otherwise it would not know which folder to use.

A waiting action resumes on its own once the thing it depends on is resolved. This is also why an Image added to product automation does not re-trigger itself: images the automation creates are tracked, so an Edit images with AI action never re-processes its own output in a loop.

Run history

Open an automation and switch to the Runs tab to see when it fired. Each run shows Triggered at, Status (Queued, Running, Paused, Retrying, Completed, Failed, Cancelled), Progress, Duration and any Error. Use View logs on a run to see every AI request and response behind it.

Tips & gotchas

Caution

Turn Auto-apply off while you are still tuning the prompt for an action. Once the output is consistently good, switch it on so the automation runs hands-free.

Tip

Use Priority when two automations react to the same event — for example, run a content-cleanup automation before an SEO one so the SEO step works on the cleaned text.

Related

• Batch jobs
• Cost management
• API logs