# Automation - Rules

The **Automation Rules** page allows you to create and manage rules that automate various processes. This functionality helps streamline operations, improve efficiency, and ensure that specific actions are triggered automatically based on predefined criteria.

<div data-full-width="true"><figure><img src="/files/gBSpYrgDET6KPU4hRHlO" alt="" width="563"><figcaption></figcaption></figure></div>

Rules are used to automate processes and consist of the following components:

* Rule Type
* Trigger
* Period
* Condition
* Value
* Actions

Each rule type comes with its own set of available triggers. Every trigger, in turn, is linked to a specific set of periods, conditions, and values. The available actions depend on the selected trigger, the account level, and user permissions.

***

### Trigger list

| Trigger               | Applies to                | Triggered when                                                          |
| --------------------- | ------------------------- | ----------------------------------------------------------------------- |
| **Status**            | SIM and Satellite         | the status changes to the selected value (e.g., Activate/Suspend)       |
| **IMEI**              | SIM only                  | the IMEI changes                                                        |
| **Date**              | SIM and Satellite         | the specific date is reached (e.g., activation date, contract end date) |
| **Data left**         | Prepaid                   | the remaining data balance falls to or below the specified threshold    |
| **Data used**         | Subscription, PAYGO, Pool | total data usage reaches the defined limit                              |
| **Voice used**        | SIM only                  | voice usage reaches the specified number of minutes                     |
| **Funds used**        | PAYGO only                | the user has spent the defined amount of funds                          |
| **Remaining balance** | Wallet only               | the wallet balance drops to the specified amount or lower.              |

The rule should be triggered once the condition for the trigger is met. After that, it should perform all actions specified in the rule.

{% hint style="success" %}
The rule should check the trigger immediately after assignment.
{% endhint %}

***

### Action list

* **Change status** – Change the status of the entity to the specified one
  * **Suspended** – Only applicable to the IMEI trigger
  * **Activate/Suspended**
* **Email notifications:**
  * **Default account email** – Send a notification email to the default account email
  * **Staff** **email** – Send a notification email to the selected staff email
  * **Company email**– Send a notification email to the default company email
  * **End user**  **email**– Send a notification email to the owner’s email
  * &#x20;**Custom email(s)** – Sends a notification to one or more manually specified email addresses (maximum of 5).
* **Enable throttle** – Sends a request to the Integrator to activate throttling (if supported by the operator).
* **Push API** – Send a webhook to the specified API endpoint.


---

# 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://faq.droam.com/menu/automation-rules.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.