Skip to main content
Automations let you set up rules that automatically enrich products as they’re created or updated. Pick a taxonomy and category, choose which attributes to generate, optionally narrow with filters, and Cernel handles the rest. Every product that matches your rule is enriched without anyone lifting a finger.

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

Products get descriptions, meta titles, and structured attributes the moment they arrive or change. No one has to remember to trigger enrichment.

Consistent coverage across your catalog

Every product that matches your rules gets the same treatment. No products slip through without content.
Key concept: when, then. Each automation is a rule: when a new or updated product in [category] matches [filters], then enrich [attributes]. Its Run setting decides how often: Once per product enriches each product a single time, and When attributes are updated enriches it every time one of the Trigger attributes you pick is updated.

Before you begin

To create an automation, you need:
  1. A category with attributes: the category must have attributes configured with linked AI agents
  2. At least one linked agent: only attributes with agents appear in the attribute picker

Creating an automation

1

Open Automations

Go to Tools > Automations in the sidebar. You’ll see a list of existing automations, each shown as a compact sentence summary so you can scan the configuration at a glance.
The Automations page listing existing automations as sentence summaries with Name, Configuration and Active columns, an Active toggle and a three-dot row menu on each row, and a Create automation button. The built-in Cernel Classification Automation shows a System badge and no row menu
2

Click Create automation

Click Create automation to open a blank automation on its own page. Give it a name in the Unnamed automation field at the top, then fill in the When and Then cards below.
The new automation page with the When card (Category, Run with Once per product and When attributes are updated, and Filter with a Search within variants toggle) and the top of the Then card with its Attributes field
3

Pick a taxonomy and category

In the When card, under Category, click Pick a taxonomy and category. A popover opens with a taxonomy selector at the top and an expandable category tree below. Pick a taxonomy, then choose any category in the tree, or pick Unclassified products to target products that haven’t been classified yet.
The taxonomy and category popover open from the Category field of the When card, showing a Cernel Taxonomy dropdown, a search field, and a tree of categories with Unclassified products at the bottom
Switching taxonomies or categories after you’ve chosen attributes or filters clears them: attributes and filters are scoped to the category you picked.
4

Choose when it runs

Under Run, choose how often the automation enriches a product:
  • 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.
The trigger attribute picker lists the category’s own attributes first. Below them, Other attributes lists every other attribute in your organization, such as a property your integration maps in (for example a variant’s color). An update to one of those can rerun the automation too. The Then card still only offers attributes set up on the category, because Cernel can only enrich an attribute the category has.
Every enrichment counts as an update, so trigger attributes can start a loop: an automation that reruns on an attribute it enriches itself, or two automations that keep starting each other. Cernel checks for this as you edit, marks the attributes that close the loop in red under These trigger attributes would start a loop, and won’t save an active automation until you remove the loop. A paused automation can be saved, but it can’t be turned on until the loop is gone.
5

(Optional) Narrow down with filters

Under Filter, the line starts as “All products are included.” To restrict the automation to a subset, click Add filter and add one or more conditions on attribute values or product properties, such as Has images or Completeness (Some tracked attributes have no value). Join conditions with and or or, the same way as in the Catalog’s filter builder.
Filters are optional. Leave them empty if you want every product in the category to be enriched.
6

(Optional) Search within variants

By default the filters match top-level products only. Turn on Search within variants, beside the filter, to let them match product variants too. A variant is then tested against the values it inherits from its parent, so a filter such as Brand is Osprey matches the parent and every variant beneath it that has no brand of its own. With no filters, the line reads “All products and variants are included.”
The When card of an automation, with the Filter line and the Search within variants toggle beside it
With this on, Product Scope is measured from each match rather than from each top-level product: Selected products only enriches exactly the products and variants that match, Include product variants adds everything below each match, and Product variants only runs only on what sits below the matches. See Variants and inherited values.
7

Pick attributes to enrich

In the Then card, under Attributes, click Add attribute. Choose one or more attributes. Only attributes that have an AI agent linked appear here. Add as many as you need; each one becomes a chip, and Add attribute adds the next. All of them run each time, in the order their dependencies need.The picker lists the attributes the category carries itself first, and then, under a From subcategories heading, the attributes defined at categories below it. Each subcategory attribute is labelled with the category it comes from, so you can pick attributes for a whole branch (for example every attribute across Clothing › Shoes, Pants, and Tops) from one automation on the parent category. Picking these attributes is safe: at run time each product only gets the attributes that apply to its own category, so a Shoes attribute simply resolves to nothing on a Pants product.To tick a run of attributes at once, click the first one, then hold Shift and click another: every attribute between the two is ticked (or cleared, if you started from a ticked one). This is the same range-select the enrichment modal in the Catalog uses, so building a long attribute list is quick.
8

(Optional) Set enrichment options

Below the attributes, the enrichment options control how each run behaves: product scope, whether values go through Review, whether to fill only missing fields, and per-language generate/translate/skip choices. The defaults work for most automations, so you can skip this and adjust later. See Enrichment options for what each control does.
9

Save the automation

Check the In short summary, which reads the automation back, for example “Every product in Shoes gets Description once, and again whenever Title is updated.” Toggle Active in the top-right if you want the automation running immediately, then click Create automation. If anything is missing, Cernel lists it under Before you can save:.
Your automation is created and appears in the Automations list. Matching products will be enriched automatically with the selected attributes.

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.
The Then card of an automation showing the enrichment options: a Product Scope selector (Selected products only, Include product variants, Product variants only), a Review toggle, an Only enrich missing fields toggle, and a Language Configuration panel with Generate, Translate, and Skip choices per language
  • 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.
A language cannot be both a target for enrichment and a translation source for another language at the same time. If you select the same language for both, the page flags the conflict so you can resolve it before saving.

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.
An automation detail page on the Overview tab, with the When card showing its category, the Once per product run setting, and a filter with two groups

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.
To edit an automation’s configuration or view its run history, click anywhere else on the row to open its detail page.

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:
The Run history tab on the automation detail page showing a table with Status, Products, Reason, and Started columns, with multiple rows of completed runs
Each row shows:
  • 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
Expand a row to see the individual products processed in that run, with links into the product detail view.

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.
Cernel ships with a built-in Cernel Classification Automation that classifies unclassified products into the Cernel Taxonomy. It appears in the Automations list with a System badge and can be paused but not edited or deleted.

Frequently asked questions

Yes. A newly created product, or an existing product that changes (for example through an integration sync or a manual edit), becomes eligible, and the automation enriches it if it matches your conditions. With Run set to Once per product, the automation enriches a given product only once, so a product it has already processed is not enriched by it again on a later change. Set Run to When attributes are updated to have it enrich the product every time one of its trigger attributes is updated instead. Such an automation runs only on those updates, so an existing product whose trigger attributes don’t change isn’t enriched by it. To enrich a batch of products on demand, use manual enrichment from the Catalog instead.
Yes, when its Run setting is When attributes are updated. The automation enriches a matching product every time one of the Trigger attributes you picked is updated in the primary language, by an integration sync, by a person, or by another automation. It doesn’t give each product a first run of its own: a change to any other attribute, a new classification, or a sync that only touches other fields starts nothing. A trigger attribute doesn’t have to be set up on the category: pick one under Other attributes to rerun the automation when, for example, your integration sends a new value for a mapped property. Every attribute in the automation runs each time. A change on a variant doesn’t rerun its parent product; turn on Search within variants to match the variants themselves. To limit the cost of, for example, an integration that sends a pushed value back in a different format, one automation runs on a given product at most 5 times in 24 hours. An update past that limit is not queued: the product runs again on its next update once the 24 hours allow it.With Once per product, the default, the automation fires on a given product at most once, even if the product is later edited or synced again. A different automation can still process the same product, and you can always re-enrich on demand with manual enrichment from the Catalog.
Every enrichment counts as an update. An automation that reruns on an attribute it enriches itself, or two automations that each enrich the other’s trigger attribute, would keep starting each other. Cernel checks for this while you edit, marks the attributes that close the loop in red, and won’t save an active automation until you remove one of them from the Trigger attributes. A paused automation can be saved with the loop, but it can’t be turned on until the loop is gone.
Check these things:
  1. 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.
  2. 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.
  3. Are the attributes still configured? The selected attributes must have AI agents linked. Check the category’s attribute configuration.
  4. 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.
  5. 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.
Changes take effect for the next products that match. Products currently being processed complete with the previous configuration; products evaluated after you save use the new configuration.
Yes. You can create multiple automations with different attributes and filters for the same category. Each runs independently when its conditions are met. For example:
  • 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)
Yes. When you pick attributes, the picker offers the ones the chosen category carries itself and, under a From subcategories heading, the ones defined at categories below it, each labelled with the category it comes from. So a single automation on a parent category can cover attributes that differ from leaf to leaf, instead of one automation per leaf. Each product still only gets the attributes that apply to its own category, so an attribute from a sibling branch simply resolves to nothing on products it doesn’t apply to.
Open the automation and switch to the Run history tab. Failed runs show a red Failed badge; expand the row to see which specific products encountered errors and follow the link into the product detail view.
Optional. If you’re importing a large batch and don’t want each new or updated product to enqueue a job, pause the relevant automations first, complete the import, then resume them and manually enrich the batch on your own schedule.
Yes. Use the Language Configuration panel in the automation’s enrichment options. Set any language to Skip to leave it out, Generate to write fresh content for it, or Translate to derive it from another language. Only the languages you set to Generate or Translate are enriched by the automation.
It depends on the Review toggle in the automation’s enrichment options. With Review on, generated values wait on the Review surface for your approval before they go live. With Review off, they’re applied to your products automatically. The toggle starts from your organization’s approve-before-push setting, and you can override it per automation.
It’s a built-in system automation that classifies products into the Cernel Taxonomy when they don’t have a Cernel category yet. You can pause it from the list view if you want to take full control of classification, but it can’t be edited or deleted.

What’s next

AI Agents

Make sure your agents are configured before setting up automations. Automations use linked agents to generate content.

Enriching products on demand

Manually enrich products that automations don’t cover, or kick off a one-off run for a specific batch.