> For the complete documentation index, see [llms.txt](https://docs.baas.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baas.sh/baas-console/automations/create-an-automation.md).

# Create an automation

Create an automation in the Console, configure its trigger, add your first actions, and activate it.

Creating an automation takes two fields. Everything it does is configured right after, on its **Pipeline** tab. For an overview first, see [how an automation works](/baas-console/automations.md).

{% stepper %}
{% step %}

### Open the Automations page

In the sidebar, open **Automations**. On your first visit, the page reads "No automations" and offers a **Create an automation** button. Once the list has entries, **New automation** at the top does the same thing.
{% endstep %}

{% step %}

### Name it

The **New automation** panel asks for two things:

* **Automation name** (required), for example `Transfer alerts`.
* **Description (optional)**, a short note on what the automation does.

Names are unique: if the name is already taken, pick another.
{% endstep %}

{% step %}

### Create

Click **Create**. You land on the automation's page, on the **Pipeline** tab. Note the **Inactive** badge in the header: a new automation starts inactive, so you build its pipeline first and activate it last.
{% endstep %}

{% step %}

### Configure the trigger

Click **Configure** on the **Trigger** node and pick a [trigger type](/baas-console/automations/triggers.md). The panel then shows that type's fields.
{% endstep %}

{% step %}

### Add steps

Once the trigger is configured, the **Add step** button below the pipeline unlocks. Each step is an action: pick its [type](/baas-console/automations/actions.md), fill in its form, and save. Actions run from top to bottom; drag a node to reorder them.
{% endstep %}

{% step %}

### Turn it on

With the trigger and at least one action in place, switch the automation to [**Active**](/baas-console/automations/manage-an-automation.md) with the toggle in the header.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**That's it.** The automation now runs every time its trigger fires, and each run shows up in the [Runs tab](/baas-console/automations/runs-and-logs.md) as it happens.
{% endhint %}

## Next

* [Runs and logs](/baas-console/automations/runs-and-logs.md): watch your automation run and read the logs.
* [Manage an automation](/baas-console/automations/manage-an-automation.md): activate, rename, or delete it.