> ## Documentation Index
> Fetch the complete documentation index at: https://help.cloudtalk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Conditions

> Learn how to use Conditions in your Workflow Automations

> [!NOTE]
>
> Workflow Automations are designed to make the job of an agent easier by automating processes such as sending a followup text, transcribing certain calls, or automatically forwarding transcriptions to Slack. *Conditions* are optional modifiers we can add to the automation process in order to specify a desired scenario to our needs.

**User level:** Admin

***

## How do Conditions work?

A *condition* is sort of like an additional "if" statement layered on top of your [trigger](/en/articles/5648924-triggers). The type of trigger you choose will alter what conditions you can add on.

Say you wanted an automation to occur when an SMS was received by a particular important contact whose phone number was 555-5555. Your Trigger would be **SMS received**, and your conditions might look like:

```text theme={"system"}
Only continue if...(Property)event.properties.sender > (Operand)contains > (Value) 5555555
```

Instead of triggering an automation each time *any* SMS is received, you are clarifying to the system that you only want the process to happen in response to a specific phone number that you've entered.

## Building a Condition

In the Workflow Automations tab under Settings, we are given the option to **+ Add Workflow**. After we have named our new Workflow and selected a Trigger, we are given the option to **Add Condition**s.

![](https://mintcdn.com/cloudtalk/0B2VFDHod1TeIVNA/images/help-center/articles/5649346/8222a9d860e6-image.png?fit=max\&auto=format\&n=0B2VFDHod1TeIVNA\&q=85\&s=344b227471e81a1a059b65fd7ca45f75)

Conditions consist of three main parts, labeled:

* [**Property**](#h_2d0ee798ba)

* [**Operand**](#h_0e8ff6bc6f)

* [**Value**](#h_f9955ed732)

## Choosing a Property

Properties must be selected from one of the phrases listed in the **Useful data for your Workflow** box. This is necessary for the system to understand your request. Key phrase options will be different depending on the Trigger you have chosen.

1. Click into the box labeled **Property.**

2. From the **Useful data for your Workflow** column, click which property you would like to use.

3. The dynamic property reference should automatically populate the field.

   ![](https://mintcdn.com/cloudtalk/0B2VFDHod1TeIVNA/images/help-center/articles/5649346/a737b593f98e-messages.png?fit=max\&auto=format\&n=0B2VFDHod1TeIVNA\&q=85\&s=bb7ee30e4e00bdaa3766fb0e48306fe1)

## Selecting an Operand

An *operand* can search for something or make a comparison. It is important for the **Property** value in your trigger to match the functionality of the operand. Use numerical values for operands which imply a number evaluation:

* is less than

* is greater than

* is less than or equal to

Other operands can additionally function with character inputs, also called *strings*. These are:

* starts with (letter/s)

* ends with (letter/s)

* contains

* is equal to (in strings, will look for exact match)

## Inputing Values

The *value* is what your condition will either be searching for or comparing the **Property** input to. Value input must be accurately paired with the **Property** input. Always refer to the **Useful data for your Workflow** sidebar to see appropriate **Value** examples for each property type.

![](https://mintcdn.com/cloudtalk/0B2VFDHod1TeIVNA/images/help-center/articles/5649346/977c1cecdba6-condition.png?fit=max\&auto=format\&n=0B2VFDHod1TeIVNA\&q=85\&s=d90d912b2ded3d2a5cff39a1e4819184)

**Numerical values** are evaluated based on standard, base ten number order.

**Strings** are evaluated based on the placement order of each character. This means incorrectly spelled words will not be recognized. Conditions are also case sensitive. A value entry of `lead` (lowercase) will not match tags which contain `Lead` (uppercase).

## Combining Multiple Conditions

This will require the selected trigger to match all condition rules in order for the resulting automation Action to take place. Click **+ Add condition** to add additional specifications to your desired scenario. You can also delete conditions by clicking the **red trash icon** or the **three vertical dots** on the upper right corner of the *Conditions* box.

![](https://mintcdn.com/cloudtalk/0B2VFDHod1TeIVNA/images/help-center/articles/5649346/175678ab185c-condition.png?fit=max\&auto=format\&n=0B2VFDHod1TeIVNA\&q=85\&s=379bb57ca4453d5d627c5f15e5808d6f)

***

*Need help or have a question?* Just reach out through our [Support portal](https://support.cloudtalk.io/hc/en-us/requests/new?ticket_form_id=26305535257884) — we’re here for you.


## Related topics

- [Caller-Based Routing with Conditions](/en/articles/5763009-caller-based-routing-with-conditions.md)
- [Configuring Workflow Automations](/en/articles/5450779-configuring-workflow-automations.md)
- [Skill Based Routing in Call Flow](/en/articles/5802573-skill-based-routing-in-call-flow.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.