> For the complete documentation index, see [llms.txt](https://docs.flowlity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowlity.com/how-tos/set-up-automation.md).

# Set up an automation

Create an automation, pick a view scope, define actions and schedule, and monitor runs.

This guide walks you through creating an automation that runs on a schedule, applies actions to a set of products, and can be monitored over time.

{% stepper %}
{% step %}
**Prepare a view for the scope**

Automations target a saved view from the Demand or Planning module. If you don't already have a suitable view, create one first — see [Set up and manage views](/how-tos/set-up-views.md).

The view's filters determine which products the automation will process. For example, a view filtering for "Overstock" products means the automation will only act on products currently flagged as overstock.
{% endstep %}

{% step %}
**Create the automation**

Go to the [Automations](/modules/automations.md) module and click **Create one automation**. Fill in:

* **Name** — A descriptive name (e.g. "Weekly overstock buffer adjustment").
* **Scope** — Select the saved view you prepared in the previous step.
* **Schedule** — Configure when the automation runs:
  * **Repeat** — Frequency (e.g. every week).
  * **On** — Days of the week.
  * **At** — Time of day.
  * **Ends** — Optional end date.
* **Action** — Define what the automation does. Use **+ Add action** to add one or more actions (e.g. set a buffer policy, apply a tag, trigger an alert).

Click **Create & Activate** to save and immediately enable the automation.
{% endstep %}

{% step %}
**Verify the first run**

After the first scheduled run (or trigger one manually using the **Run manually** button):

1. Open the automation's detail panel.
2. Switch to the **Runs** tab.
3. Check the run status — it should show *Successfully* with the number of products processed.

If the run shows an error, review the automation's scope and action configuration.
{% endstep %}

{% step %}
**Monitor ongoing runs**

The automation list shows the **Last run / Next run** dates and total **Runs** count for each automation. Use the **Runs** tab in the detail panel to review the history of all past executions.

{% hint style="info" %}
Start with a narrow view scope and simple action to test the automation, then broaden it once you are confident it works as expected.
{% endhint %}
{% endstep %}
{% endstepper %}

### Related pages

* [Views and filtering](/concepts/views-and-filtering.md) — How views work and their role as automation scope.
* [Set up and manage views](/how-tos/set-up-views.md) — Create the view you need for the automation scope.
* [Automations](/modules/automations.md) — Full reference for the Automations module.