# Copy of 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.

{% tabs %}
{% tab title="Dictionary" %}
General Terms from the **Automation** page:

* **Name -** The identifier for the rule.
* **Type -** The type of entity the rule applies to (e.g., SIM, Pool, Account).
* **Period -** The timeframe or cycle during which the rule is active (e.g., billing cycle, permanent, refill cycle).
* **Trigger -** The event or condition that activates the rule (e.g., status change, specific date, remaining balance).
* **Plan Type -** The type of plan to which the rule applies.
* **Condition -** The specific criteria that must be met for the rule to trigger.
* **Action -** The action that will be taken when the rule is triggered (e.g., suspend, activate, send email notification).
* **Created By -** The initiator of the rule.
  {% endtab %}

{% tab title="Key Features" %}

1. **Detailed Information:** Clicking on a specific row provides additional details:
   * **SIMs:** Displays the number of SIMs affected by the rule.
   * **General:** Provides an overview including the rule’s name, period, type, plan type, and description.
   * **Condition:** Details the trigger, condition, value, and specific action to be taken. 
   * **Action:** Specifies what actions will be performed when the rule is triggered, including email and push notifications. Includes options for email notifications (on/off), push API notifications (on/off), and additional email settings for end users and companies.

#### 2. Rule Logs <a href="#rule-logs" id="rule-logs"></a>

Tracks the history of rule executions with:

* **Date:** When the action was triggered.
* **Destination:** The recipient of the notification or action.
* **Trigger:** The condition or event that activated the rule.
* **Rule:** The name or identifier of the rule. This field is available only when the transaction was made manually.
* **Action:** The action is taken when the rule is triggered.

Rules can help to automate repetitive tasks and ensure timely responses based on specific conditions. By setting up automation rules, you can efficiently manage operations, reduce manual effort, and ensure that actions and notifications are handled consistently and automatically.&#x20;

This helps in optimizing workflow, maintaining operational efficiency, and ensuring that critical processes are executed without manual intervention.
{% endtab %}
{% endtabs %}


---

# 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/copy-of-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.