# Automations

An automation is a specific flow that, given a specific rule will, if valid, execute a set of pre-defined actions. At this moment, automations get assessed for each new ingested trace and check.

You can view all your existing automations by clicking on `Automations` in the sidebar.

| Automation Attribute | Description                                                                                                                                                                                                                                         |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**             | A name for the automation to easily identify it later.                                                                                                                                                                                              |
| **Enabled**          | Whether the automation is currently enabled. If disabled, the automation will not be evaluated and will never trigger. This is useful for drafts.                                                                                                   |
| **Sampling Rate**    | How often the automation should be evaluated, between 0 and 1. A value of 1 means every time, 0.5 half the time, and 0 never.                                                                                                                       |
| **Rule**             | Each automation has a set of rules that determine when it should trigger. The rules are evaluated against the incoming data.                                                                                                                        |
| **Actions**          | <p>The actions to perform when the automation triggers. You must ensure your actions work with the resource type detected from the rule (<code>trace</code>).<br><br>The currently available actions are:<br>- Send Webhook<br>- Run Evaluation</p> |

{% hint style="warning" %}
**An automation can only target one resource type (i.e., trace, check).** Therefore, an automation rule such as `trace.name == "some-name" && check.outcome == "pass"` will always be skipped. If you need to run the same set of actions for both resources, create two distinct automations.
{% endhint %}

### Create/Edit an automation

To create an automation:

1. Go to `Automations`
2. Click on `+ New`

To edit an automation:

1. Go to `Automations`
2. Click `Edit` for the automation you want to change

### Delete an automation

1. Go to `Automations`
2. Click `Edit` for the automation you want to change
3. Click the `Delete automation` button


---

# Agent Instructions: 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:

```
GET https://docs.modelmetry.com/platform/automations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.