IF conditions

IF conditions allow you to add more logic to your Recipe flow. Escalate urgent support tickets by checking the priority with an IF condition or use the IF condition to check for a valid email before sending an onboarding greeting.

IF conditions can be found in multiple features in AppConnect:

Conditions

Each condition consists of 3 parts - data, condition and value. Conventionally, the data (left-hand-side) is the variable data from your app, e.g. case status, or lead rating. Accordingly, the value (right-hand-side) is the static value you wish to check against, e.g. "Closed" or "Hot", correspondingly. Data and values are case sensitive.

In this article, we go through the 14 conditions you can choose from. We will be using trigger conditions as examples. Additionally, you can combine multiple conditions with the AND or OR operators to set up complex conditions.

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.

Furthermore, if an invalid IF condition was set up for triggers, the Recipe might:

• throw a trigger error after the recipe has started, resulting in the inability to pick up trigger events, or

• result in the recipe filtering out all trigger events.

Contains

This condition checks if the data contains the value. It is case-sensitive - make sure to downcase or upcase both before comparison if you are not concerned about case sensitivity. It works with any characters, numbers, words, letters, and symbols.

Valid types

This condition is only valid for array and string data types.

Starts with

This condition checks if the trigger data string begins with the value. It is case-sensitive - make sure to downcase or upcase both before comparison if you are not concerned about case sensitivity.

The Starts with condition searches only for exact matches, and null values will not be picked up.

Valid types

This condition is only valid for string data types.

Special non-string data type cases

When we try to compare non-string data types with a starts with condition, it will throw a trigger error. For example, comparing a number type with a number type will throw an error.

However, if the trigger data input field is a non-string datapill, and the value is a string, AppConnect converts the datapill's value into a string value for you and does the comparison, evaluating to true if the converted value meets the condition.

Ends with

This condition checks if the trigger data ends with the value. It is case-sensitive - make sure to downcase or upcase both before comparison if you are not concerned about case sensitivity. It works with any characters, numbers, words, letters, and symbols.

If the field you specify in your condition is left blank in the application you’re using, no event will be picked up.

Valid types

This condition is only valid for string data types.

Special non-string data type cases

When we try to compare non-string data types with a ends with condition, it will throw a trigger error. For example, comparing a number type with a number type will throw an error.

Comparing number types for ends with condition will throw a trigger error

However, if the trigger data input field is a non-string datapill, and the value is a string, AppConnect converts the datapill's value into a string value for you and does the comparison, evaluating to true if the converted value meets the condition.

Does not contain

This condition is the opposite of the contains condition. It checks if the trigger data DOES NOT contain the value. It is case-sensitive - make sure to downcase or uppercase both before comparison if you are concerned about case sensitivity.

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.

Valid types

This condition is only valid for array and string data types.

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 is case-sensitive - make sure to downcase or uppercase both before comparison if you are concerned about case sensitivity.

If the field you specify is left blank in the application you are using, the Doesn’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.

Valid types

This condition is only valid for string data types.

Special cases

Non-string data types

When we try to compare non-string data types with a doesn't start with condition, it will throw a trigger error. For example, comparing a number type with a number type will throw an error.

Comparing number types for doesn't start with condition will throw a trigger error

However, if the trigger data input field is a non-string datapill, and the value is a string, AppConnect converts the datapill's value into a string value for you and does the comparison, evaluating to true if the converted value meets the condition.

Nil/null

When the trigger data is nil (also known as null), the trigger event will not be picked up by the recipe, even if it seems like it matches the condition, e.g. nil doesn't end with "345".

Does not end with

This condition is the opposite of the ends with condition. It checks if the trigger data DOES NOT end with the value. It is case-sensitive - make sure to downcase or upcase both before comparison if you are not concerned about case sensitivity. It works with any characters, numbers, words, letters, and symbols.

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.

Valid types

This condition is only valid for string data types.

Special cases

Non-string data types

When we try to compare non-string data types with a doesn't end with condition, it will throw a trigger error. For example, comparing a number type with a number type will throw an error.

However, if the trigger data input field is a non-string datapill, and the value is a string, AppConnect converts the datapill's value into a string value for you and does the comparison, evaluating to true if the converted value meets the condition.

Non-string datapills will be converted to a string for comparison if value is a string.

Nil/null

When the trigger data is nil (also known as null), the trigger event will not be picked up by the recipe, even if it seems like it matches the condition, e.g. nil doesn't end with "345".

Equals

This condition checks if the trigger data equals the value. It is case-sensitive - make sure to downcase or upcase both before comparison if you are not concerned about case sensitivity. It works with any characters, numbers, words, letters, and symbols.

Valid types

This condition is valid for all data types, e.g. booleans, string, integers and floats, dates, arrays.

Special string conversion cases

When we try to compare a non-string data type trigger data to a string data type value, AppConnect will convert the trigger data into string for comparison, e.g. 12345 equals "12345" will evaluate to true.

Does not equal

This condition is the opposite of the equal condition. It checks if the trigger data DOES NOT equal the value. It is case-sensitive - make sure to downcase or uppercase both before comparison if you are concerned about case sensitivity. It works with any characters, numbers, words, letters, and symbols.

Valid types

This condition is valid for all data types, e.g. booleans, string, integers and floats, dates, arrays.

Greater than

This condition checks if the trigger data is greater than the value.

If 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, date, timestamp, integer and number data types.

Less than

This condition checks if the trigger data is less than the value.

If 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, date, timestamp, integer and number data types.

Is true

This condition checks that the trigger data 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 evaluates to a boolean.

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 formula that evaluates to true or false.

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 evaluates to a boolean.

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 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, e.g. booleans, string, integers and floats, dates, arrays.

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 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, e.g. booleans, string, integers and floats, dates, arrays.