How it works
An automation watches for products in a specific taxonomy and category. When a product arrives or changes in a way that matches your conditions, Cernel automatically runs enrichment using the agents linked to the attributes you selected. The results appear as jobs you can review from the Dashboard and on the automation’s Run history tab. You configure an automation on one page with two cards. When says which products the automation picks up and when it runs; Then says which attributes it enriches and how. An In short line below them reads the automation back as a sentence while you edit it.Why you would use this
No content bottleneck for new or changed products
Consistent coverage across your catalog
Before you begin
To create an automation, you need:- A category with attributes: the category must have attributes configured with linked AI agents
- At least one linked agent: only attributes with agents appear in the attribute picker
Creating an automation
Open Automations

Click Create automation

Pick a taxonomy and category

Choose when it runs
- Once per product: each matching product is enriched a single time, when it’s created or when it’s first updated by a sync, by a person, or by another automation. This is the default.
- When attributes are updated: each matching product is enriched every time one of its Trigger attributes is updated in the primary language, whether by an integration sync, by a person, or by another automation. An update to a value the product inherits from its parent counts too. Nothing else starts a run: a new product, or a change to any other attribute, doesn’t on its own. A new product that arrives with a value for a trigger attribute does run, because setting that value is an update. Values that were already in place before you saved the automation don’t start a run. Pick at least one trigger attribute. Every attribute in the Then card runs each time.
(Optional) Narrow down with filters
(Optional) Search within variants

Pick attributes to enrich
(Optional) Set enrichment options
Save the automation
Enrichment options
In the Then card, every automation carries the same enrichment options as a manual enrichment run, so an automation and a hand-started run behave identically. These options are saved with the automation and applied to every run it triggers.
- Product Scope: whether the automation enriches the matched products only, includes their variants, or runs only on the variants. Pick Include product variants or Product variants only when your enrichment should reach variants beneath the products that match.
- Review: when on, generated values are held as pending on the Review surface for approval before they go live. When off, values are applied to your products automatically. The starting position follows your organization’s approve-before-push setting, and you can override it per automation.
- Only enrich missing fields: when on, existing values are left untouched and enrichment runs only for attributes that are currently empty. Use this when you want an automation to backfill new products without overwriting content you have already reviewed or hand-edited. A value a variant inherits from its parent counts as present, unless the attribute’s Variants inherit this from their parent setting is off. Leave it off for an automation that runs When attributes are updated: a run after an update would find every attribute already filled and change nothing, and Cernel warns you when both are on.
- Language Configuration: for each language, choose whether the AI generates content from scratch, translates it from another language, or skips it. Use Translate from to set the source language for a translated language, and Apply to all to set the same mode for every language at once.
Variants and inherited values
When Search within variants is on, an automation also picks up variants whose inherited values change. If a parent product’s value changes, Cernel re-checks the variants beneath it against the automation’s filters, so a variant that now matches through its parent is enriched on the next run. What a variant inherits is decided per attribute by the Variants inherit this from their parent setting in the automation’s taxonomy (see Enrich variants from their own data only). Where it is off, a variant matches a filter on that attribute only through its own value.Managing automations
Click any row in the Automations list to open the automation’s detail page. The detail page uses the same When and Then cards as creation: change anything in place, then click Save changes. Toggle Active in the top-right to pause or resume without losing the configuration, and use the red delete icon to remove an automation permanently.
List-view actions
You don’t have to open the detail page for quick changes. Each row in the Automations list carries two controls:- Active toggle: the switch on the right of each row pauses or resumes the automation in place. A paused automation stops processing products until you switch it back on.
- Row menu: opens a short menu whose one action, Delete, removes the automation permanently. Deleting from here warns you first, just like the detail page does. The built-in Cernel Classification Automation can’t be deleted, so it shows no row menu.
Viewing run history
Each automation detail page has a Run history tab next to Overview. The tab lists the runs that have processed products for this automation:
- Status: Done (green), Running (blue), Pending (yellow), or Failed (red)
- Products: How many products the run processed
- Reason: why the run started: First run for an automation that runs once per product, or Trigger attribute updated for an automation that runs when attributes are updated
- Started: Relative time the run began
Multi-taxonomy and Unclassified products
Each automation is scoped to one taxonomy and category. If you have several taxonomies on the same products, create one automation per taxonomy / category combination; they run independently and write into different attribute sets. You can also pick Unclassified products as the category. An Unclassified automation targets products that haven’t been classified into the chosen taxonomy yet, and is limited to setting the classifying attribute of that taxonomy so the automation can place the product in the right category before any further enrichment runs.Frequently asked questions
Does an automation run on existing products too?
Does an automation run on existing products too?
Can an automation run on the same product more than once?
Can an automation run on the same product more than once?
Why does Cernel say my trigger attributes would start a loop?
Why does Cernel say my trigger attributes would start a loop?
Why isn't my automation triggering?
Why isn't my automation triggering?
- Is the automation active? Paused automations don’t process products. Check the Active toggle, either the switch on the automation’s row in the list or the Active switch on its detail page.
- Do the conditions match? If you set filters, products must match them. Open the automation and check the When card; remove a filter temporarily to test.
- Are the attributes still configured? The selected attributes must have AI agents linked. Check the category’s attribute configuration.
- Has it already run on the product? With Run set to Once per product, a product the automation has already processed isn’t enriched by it again. Switch to When attributes are updated if it should run again when certain attributes change.
- Did a trigger attribute change? With When attributes are updated, the automation runs only when one of its Trigger attributes is updated in the primary language after you saved the automation. A new product, or a change to another attribute, doesn’t start it. Add the attribute that changes to the Trigger attributes, or use manual enrichment from the Catalog for products that are already in place.
What happens if I edit a running automation?
What happens if I edit a running automation?
Can I have multiple automations for the same category?
Can I have multiple automations for the same category?
- Automation 1: Cernel Taxonomy › Apparel → Meta Title, Meta Description (basic SEO for everything)
- Automation 2: Cernel Taxonomy › Apparel, filtered to has images → Product Description, Materials (rich content only where the AI can see the product)
Can one automation enrich attributes that live on subcategories?
Can one automation enrich attributes that live on subcategories?
How do I know if an automation failed?
How do I know if an automation failed?
Should I pause automations during bulk imports?
Should I pause automations during bulk imports?
Can I limit an automation to specific languages?
Can I limit an automation to specific languages?
Do automation results go through Review before they're saved?
Do automation results go through Review before they're saved?
What is the Cernel Classification Automation in my list?
What is the Cernel Classification Automation in my list?
