> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/automations/about-automations/setting-up-automations.md).

# Setting Up Automations

{% hint style="warning" %}
The system does not trigger further automations from within an automation, so infinite technical loops are prevented. However, when using AI actions (such as content generation), the generated output may differ each time, potentially causing repeated overwrites if not properly conditioned. To avoid overwriting existing content repeatedly, add a condition to prevent continuous loops. Ex. runs when the description attribute "is empty".
{% endhint %}

{% hint style="info" %}
The execution order of automation follows the sequence in which the automation tasks are created within the system. However, users can modify this order by adjusting the "Order" field for each task.
{% endhint %}

{% hint style="info" %}
For using attribute values, variables must be used. Example prompt: “Use the values of the attribute #color and #size to create a description.”
{% endhint %}

<figure><img src="/files/iXgQzJPNKwrFVVwQ71fC" alt=""><figcaption><p>Automations - Order</p></figcaption></figure>

* Any automation errors can be viewed via the *"Error log"* button located at the top-right corner of the screen.

<figure><img src="/files/Q0SJRMt9IThpoudezpcx" alt=""><figcaption><p>Automations - Error log</p></figcaption></figure>

* To enable or disable automation, use the slider next to the *"Order"* field. The default state for newly created automation is *"Disabled"*.

<figure><img src="/files/F4Lts2qJG9FrNzU0DwAV" alt=""><figcaption><p>Automations - Turn on / off</p></figcaption></figure>

* To edit, duplicate, or delete automation, click on the *"three-dot menu"* located next to the activity slider, and select the desired option.

<figure><img src="/files/0ZEcER9nmAVBEOaYCvxO" alt=""><figcaption><p>Automations - Three-dot menu</p></figcaption></figure>

* A single automation can have a maximum of  fifteen (15) Conditions and fifteen (15) Actions.

## **Key Components of Automations**

To set up an automation, you need the following elements:

1. **Trigger (When)**: The event that starts the automation.
2. **Conditions (And if)**: Criteria that define when the automation should run.
3. **Actions (Then)**: Tasks performed when conditions are met.

## **Step 1: Create a new automation**

Automations can be accessed from the left-hand side panel in the Ergonode interface:

1. Click on the "**Automations"**.&#x20;
2. If it’s your first time, you’ll see a blank screen. Click on **New Automation** to get started.

<figure><img src="/files/WmVHg06LNjcCAFom3REE" alt=""><figcaption><p>Automations - Main screen - No automations</p></figcaption></figure>

## **Step 2: Set name**

Use the field labeled "Name" to specify a clear, concise title for your automation. This name will help you and your team easily identify its purpose or function in the list of automations. Consider choosing a descriptive name that reflects the automation’s triggers, conditions, and actions, making it straightforward to locate and manage later. For instance, names like “Assign to 'Sofas' category when 'Product type' attribute value match” ensure clarity and ease of use. Take your time to make it as informative as possible!

<figure><img src="/files/j7vu45LfggfYsV1gvb50" alt=""><figcaption><p>Automations - Create automation - Name</p></figcaption></figure>

## **Step 3: Define Conditions**

Conditions specify when an automation should run. These can be based on:

* **Attribute Value**: Characteristics like material (e.g., "100% Cotton") or size (e.g., "45").
* **Category**: Product categories such as "Electronics" or "Herbal Teas."
* **Template**: Specific templates for product pages (e.g., "Furniture").
* **Status**: Workflow status changes, such as "Product Category Updated."

<figure><img src="/files/4WIhB7he9tkvjFkEH90U" alt=""><figcaption><p>Automations - Create automation - Conditions</p></figcaption></figure>

## **Step 4: Choose Actions**

Actions define what happens when conditions are met. Examples include:

* **Edit attribute value**: Modify one or more product attributes.
* **Edit category**: Change a product’s category.
* **Edit template:** Change a product’s template.
* **Edit status:** Change a product’s status.
* **Generate description/name**: Use AI to create product descriptions or names based on a custom prompt.
* **Translate**: Automatically translate attribute values into another language.

{% hint style="info" %}
AI-Powered Actions allow you to select a specific model. Keep in mind that different models consume credits at different rates.
{% endhint %}

<figure><img src="/files/8aFdEpBqbLnM2qaXROCu" alt=""><figcaption><p>Automations - Create automation - Action</p></figcaption></figure>

## **Step 5: Save the automation by clicking "Create"**

<figure><img src="/files/r3mss4np2O5qOXLoxQga" alt=""><figcaption><p>Automations - Create automation - Create</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://usermanual.ergonode.com/automations/about-automations/setting-up-automations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
