What are IF and IF/ELSE conditions?
IF and IF/ELSE conditions serve as vital components within workflow automation, offering the ability to apply conditional logic and precisely control the flow of a recipe to align with your specific workflow needs.
This type of action consists of:
1. Conditional statement
Conditional statements in workflow automation serve to evaluate whether a specific condition is true or false. These statements are constructed using data outputs from the preceding steps in the recipe.
For instance, consider the following example where the condition checks whether a candidate added has an Email ID.
2. Actions if a condition is true
A block of actions that will be executed whenever the condition evaluates to true.
3. Actions if a condition is false
A block of actions that will be executed whenever the condition evaluates to false.
This is only applicable for IF/ELSE conditions.
What are Conditions?
Each condition consists of 3 parts:
Data
Condition
Value
Conventionally, the data block on the left-hand side represents variable data from your application. For example, Email.
We'll walk you through the 14 distinct conditions available for selection. Using trigger conditions as examples, we'll provide detailed insights into how each condition operates within the context of workflow automation.
Moreover, we'll demonstrate how you can leverage the power of logical operators such as AND/OR to combine multiple conditions.
Please note: Each condition will be valid for different data types. If a condition is attempted to be used for invalid data types, it might prevent the recipe from starting successfully.
What are the different Condition types available?
1. Contains
1. Contains
This condition evaluates whether the data contains a specific value. This condition can work with any characters, numbers, words, letters, and symbols present in the data.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Valid types: This condition is only valid for array and string data types.
Examples:
2. Starts with
2. Starts with
This condition checks if the trigger data string begins with the value.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Valid types: This condition is only valid for string data types.
Examples:
3. Ends with
3. Ends with
This condition checks if the trigger data ends with the value. It works with any characters, numbers, words, letters, and symbols.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Also, if the field you specify in your condition is left blank in the application you’re using, then no event will be picked up.
Valid types: This condition is only valid for string data types.
Examples:
4. Does not contain
4. Does not contain
This condition is the opposite of the “contains" condition. It checks if the trigger data DOES NOT contain the value.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Valid types: This condition is only valid for array and string data types.
If the field you specify is left blank in the application you are using, the “Doesn’t contain” condition will not count it, and no event will be picked up. This can be circumvented by using the “Is true” or “Is not true” conditions with a string formula, as shown in the Is true section below, or by pairing it with the “Is present” condition.
Examples:
5. Does not start with
5. Does not start with
This condition is the opposite of the “Starts with” condition. It checks if the trigger data string DOES NOT begin with the value.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Valid types: This condition is only valid for string data types.
If the field you specify is left blank in the application you are using, the Don’t Start with condition will not count it, and no event will be picked up. As with the Doesn’t contain trigger condition, this can be circumvented by using a string formula with the Is True formula as shown in the Is True section below, or by pairing it with the Is present condition.
Example:
6. Does not end with
6. Does not end with
This condition is the opposite of the Ends with the condition. It checks if the trigger data DOES NOT end with the value. It works with any characters, numbers, words, letters, and symbols.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Valid types: This condition is only valid for string data types.
If the field you specify is left blank in the application you are using, the Doesn’t end with condition will not count it, and no event will be picked up. Similar to the Doesn’t contain trigger condition, this can be circumvented by using a string formula with the Is True formula as shown in the Is True section below, or by pairing it with the Is Present condition.
Examples:
7. Equals
7. Equals
This condition checks if the trigger data equals the value. It works with any characters, numbers, words, letters, and symbols.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Valid types: This condition is valid for all data types, for example, integers, and floats, dates, and arrays.
Example:
8. Does not equal
8. Does not equal
This condition is the opposite of the “Equal condition”. It checks if the trigger data DOES NOT equal the value. It works with any characters, numbers, words, letters, and symbols.
It's important to note that it is case-sensitive, so if case sensitivity isn't a concern, it's advisable to standardize the case (lowercase or capitalize) before comparison.
Valid types: This condition is valid for all data types, for example, integers, and floats, dates, and arrays.
Examples:
9. Greater than
9. Greater than
This condition checks if the trigger data is greater than the value.
If the value is set to a number, and the trigger data field has a null value, the recipe will raise a trigger error, as computationally, a number cannot be compared with a null value. To resolve this issue, add an is present condition along with the greater than condition.
Valid types: This condition is valid for string, integer, and number data types.
Examples:
10. Less than
10. Less than
This condition checks if the trigger data is less than the value.
If the value is set to a number, and the trigger data field has a null value, the recipe will raise a trigger error, as computationally, a number cannot be compared with a null value. To resolve this issue, add an is present condition along with the less than condition.
Valid types: This condition is valid for string, integer, and number data types.
Example :
11. Is true
11. Is true
It can also be used to check that the formula provided in the trigger data input field evaluates to true. For example, you can convert string type datapills via string formulas into conditions that evaluate to a boolean.
This condition is only valid for boolean data types. We can use this condition to check against a boolean datapill or check against a formula that evaluates to true or false.
Valid types: This condition is only valid for boolean data types. We can use this condition to check against a boolean datapill or check against a formula that evaluates to true or false.
Example:
12. Is not true
12. Is not true
This condition is the opposite of the “is true condition”. It checks that the trigger data “IS NOT” true.
It can also be used to check that the formula provided in the trigger data input field evaluates to false. For example, you can convert string type datapills via string formulas into conditions that evaluate to a boolean.
Examples:
13. Is present
13. Is present
This condition will check the trigger data. If there is data present, the trigger event will be picked up by the recipe. If the input is null or an empty string, the trigger event will not be picked up by the recipe.
Valid types: This condition is valid for all data types, for example, integers, and floats, dates, and arrays.
Example :
14. Is not present
14. Is not present
This condition will check the trigger data. If there is data present, the trigger event WILL NOT be picked up by the recipe. If the input is null or an empty string, the trigger event WILL be picked up by the recipe.
Valid types: This condition is valid for all data types, for example, integers, and floats, dates, and arrays.
Example:
If you have questions about these conditions, feel free to reach out to us at support@recruitcrm.io. 😄