Skip to main content

Workflow & Productivity

Automate the steps you repeat A trigger starts each run

Pick a trigger, add conditions, chain the actions: enrichment, translation, web research, field updates, notifications, webhooks and channel publishing.

  • 7 trigger types
  • Draft mode with Run Now
  • Run history with retries

Key features

  • Start on a product event

    Product created, updated, field changed, lifecycle stage changed, quality score changed, on a schedule, or on a manual run.

  • Narrow it with conditions

    Match on any attribute, quality score, status or custom field, so the run only touches the products you meant.

  • Chain the actions

    Enrich, translate, research the web, assign categories, update fields, notify the team, call a webhook, publish to a channel.

The builder

One canvas from trigger to published

Every automation is the same three parts on one canvas: what starts it, which products it applies to, and what happens to them.

The trigger sits at the top of the canvas; each node below it is one condition or action, and the run follows them top to bottom.

Every automation is three blocks

  1. Triggers

    A trigger starts the flow. A product is created, updated or imported, a field or quality score changes, a schedule fires, or you press run yourself.
    A schedule trigger set to run every night at 03:00 in your own timezone.
  2. Conditions

    A condition decides which products go on. Match all or any of its rules: an attribute value, a quality score under your threshold, a missing field, a category, a missing translation.
    The condition node. Products that fail the match stop here instead of reaching the actions.
  3. Actions

    Actions do the work: AI enrichment, translation, web research, category assignment, field updates, notifications, webhooks and publishing to a channel. Chain as many as the job needs.
    An enrichment action writing product titles. The prompt it uses is picked in the panel.
  4. Templates

    A template is the same three blocks, pre-wired for a common job: enrich on import, translate before publishing, re-check quality on a schedule. Load one, then change what you like.
    The template gallery. Load one, then edit the trigger, the conditions or the actions.

Templates

Three flows teams switch on first

Each one is a trigger, a condition and a couple of actions. Start from the template and adjust it.

  • Onboard newly imported products

    On import, enrich the empty fields, translate into your configured languages and move the product to the next lifecycle stage.

    Result: an imported product arrives ready for review instead of empty.

  • Hold products that fail the quality bar

    On update, check the quality score. Below your threshold, the product stays out of the publish stage and the owner gets a notification.

    Result: the channel only receives products that passed the check.

  • Re-run the checks on a schedule

    On a nightly schedule, re-check a segment for missing attributes or stale content and report what needs a person.

    Result: a short list each morning instead of an audit each quarter.

FAQs

Automation questions, answered

Which triggers exist, what an automation can do, what happens when a run fails, and how to test safely first.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

You can trigger automations on: product created, product updated, field changed, lifecycle stage changed, quality score changed, a scheduled time, or manually. Each trigger can be combined with conditions to control exactly which products activate the automation.

Automations can run actions like AI enrichment, translation, web research, category assignment, field updates, notifications, webhook calls, and moving products between lifecycle stages. You can chain multiple actions in a single automation.

Automations have built-in error handling. If an action fails, the automation status changes to Error and you can see the details in the run history. You can set up retry behavior and configure alerts so you are notified when an automation fails.

Yes. Save an automation as a Draft without activating it, then use the Run Now button to try it on a small set of products first. When you are confident it works, switch the status to Active.

There is no hard limit. We recommend keeping your list manageable by using clear names, archiving automations you no longer use, and grouping related actions into a single workflow where possible.

Next step

Build one automationThe trigger does the rest

Build your first automation on your own catalog, or have us map your current process onto triggers and actions on a call.