# Conditions

When setting up workflow enrollment triggers in Otomato, it's crucial to understand how **AND** and **OR** logic work to ensure your automation target the correct criteria within the Web3 space.

**AND Logic**

**AND logic** is used when you want to identify blockchain events or conditions that meet *all* the criteria specified in your workflow triggers. This means that every condition you set must be true for the action to be executed.

* **Example**: Suppose you want to trigger an automation only when the following conditions are both met:

  1. The price of ETH drops below $1500 **AND**
  2. A specific wallet receives at least 10 ETH.

  In this case, you would:

  * Set your first trigger to monitor the price of ETH.
  * Click **AND** before adding the second trigger.
  * Set the second trigger to monitor the incoming ETH to the specific wallet.

**Result**: The automation will only run when the price of ETH is below $1500 **and** the wallet receives at least 10 ETH.<br>

**OR Logic**

**OR logic** is used when you want to trigger an automation if *any one* of several conditions is met. This means that if at least one of the specified conditions is true, the action will be triggered.

* **Example**: Imagine you want to trigger an action if:

  1. The price of ETH drops below $1500 **OR**
  2. A wallet receives any amount of ETH.

  In this case, you would:

  * Set your first trigger to monitor the price of ETH.
  * Click **OR** before adding the second trigger.
  * Set the second trigger to monitor any ETH transactions to the wallet.

**Result**: The automation will trigger if either the price of ETH drops below $1500 **or** the wallet receives ETH, regardless of the amount.

#### Applying Logic in Otomato Workflows

* **AND Logic**: Use this when you need to create precise, targeted automations that only execute when all conditions are met. For instance, automating a trade only when market conditions and wallet activity align.
* **OR Logic**: Use this when you want your automation to be more flexible, triggering when any of the set conditions are met, such as sending notifications based on multiple possible events.