Conditions

Conditions

In Integration Hub recipes, IF conditions are created by defining three key components:

• Data Field: The variable data from your app (For example, case status or lead rating).

• Condition: The comparison operator used to evaluate the data field.

• Value: The static value being checked against (For example, Closed or Hot).

Note

Data fields and Values are case-sensitive

This section describes fourteen available conditions, using trigger conditions as examples. Multiple conditions are combined using AND or OR operators to create complex logic.

Each condition is designed for specific data types, and using an incompatible data type may prevent the recipe from functioning correctly.

If an invalid IF condition is set for triggers, the Recipe may:

• Generate a trigger error at startup, preventing it from capturing trigger events.

• Filter out all trigger events, causing the recipe to miss expected inputs.

Where conditions can be used

Using Conditions to Refine Your workflow:

You can apply conditions in the following features to enhance your workflow:

• IF Control Statements – Define conditions within IF statements to execute specific steps or actions based on your data.

• While Loop – Set conditions in a Repeat While loop to continue executing actions until a specified condition is met.

• Trigger Conditions – Use conditions to filter trigger events, ensuring that only relevant events are processed by the recipe.

Contains

The Contains condition checks whether a data field includes a specified value within a sequence of conditional checks. This is useful for routing or processing data based on the presence of specific content. It is the inverse of the Doesn't Contain condition and is case-sensitive. If a case-insensitive comparison is needed, you can adjust the case of both the data and value accordingly.

Figure: Else if

Compatible data types

This condition is compatible with array and string data types.

Starts with

The Starts With condition checks whether a data field string begins with a specified value in a sequence of conditions. It is the opposite of the Doesn’t Start With condition and is case-sensitive. To ensure accurate comparisons, make sure that both the data and the specified value are in the same case (either all uppercase or all lowercase).

Figure: Else if and OR

The Starts With condition only match exact strings and does not detect null values.

Compatible data types

This condition is applicable only to string data types.

Examples

Special non-string data type cases

To prevent trigger errors, avoid using the "starts with" condition to compare non-string data types. For instance, directly comparing two numeric values will result in an error.

ends with

The ends with condition checks whether a data field concludes with a specified value. It is the opposite of the doesn't end with condition and is case-sensitive. To ensure accurate comparisons, confirm that both the data and the specified value are in the same case (either uppercase or lowercase).

Figure: Else IF

If the specified field in your condition is empty in the application you’re using, no event will be captured.

Compatible data types

This condition is applicable only to string data types.

Examples

Special non-string data type cases

To prevent trigger errors, avoid using the "ends with" condition to compare non-string data types. For instance, directly comparing two numeric values will result in an error.

Figure: ends with

does not contain

The does not contain condition enables actions to be triggered when specific values are missing from data fields. It is the opposite of the contains condition and is case-sensitive. Ensure both the data and the specified value match in case (either all lowercase or all uppercase) for accurate comparisons.

Figure: does not contain Shared Folder access

Compatible data types

This condition is compatible only with string and array data types.

Examples

does not start with

The does not start with condition enables actions when a data field does not begin with a specified sequence. It is the opposite of the starts with condition and is case-sensitive. Ensure both the data and the value are in the same case (either all lowercase or all uppercase) for accurate comparisons.

Figure: does not start with - In Progress

Compatible data types

This condition is applicable only to string data types.

Examples

Special non-string data type cases

To prevent trigger errors, avoid comparing non-string data types using the "doesn't start with" condition. For instance, directly comparing two numeric values will result in an error.

Figure: does not start with

Special non-string data type cases

If your trigger data is null (nil), Integration Hub will not capture the trigger event, even if it technically satisfies the condition. For example, a null value does not start with 345.

equals

The equals condition defines actions for scenarios where a data field exactly matches a specified value. It is essential for processes that rely on precise matches. This condition is the opposite of the does not equal condition and is case-sensitive. To ensure accurate comparisons, verify that both the data and the value use the same case (either lowercase or uppercase).

Figure: equals

Compatible data types

This condition is compatible with all data types, such as Integers and floats, dates, and arrays.

Examples

#Special cases

Floats have limited precision. Comparisions with strings containing more than 15 digits may not be accurate. Use formula mode for precise comparisons in these situations.

String to numeric coercion also recognizes base-8 notation which converts 0123 o 83

This logic also applies to does not equal, greater than, and less than operations.

does not equal

The does not equal condition is used to specify actions when a data field does not exactly match a given value. It plays a key role in detecting discrepancies or variations in data. As the inverse of the equals condition, it is case-sensitive. For accurate comparisons, ensure that both the data and the value are in the same case—either all lowercase or all uppercase.

Figure: does not equal

Compatible data types

This condition is compatible with all data types, such as integers and floats, dates and arrays.

Examples

greater than

The greater than condition enables you to define actions when the value of a data field is higher than a specified number or date. It is especially useful for prioritizing tasks or records based on numerical or date-based criteria. This condition is the opposite of the less than condition.

Figure: greater than

Compatible data types

This condition is compatible with string, integer, and number data types.

less than

The less than condition defines actions when a data field's value is below a specified threshold, following an initial IF condition. It is crucial for scenarios that involve ranking or filtering based on lower numerical or date values. This condition is the opposite of the greater than condition.

Figure: Less than

If the value is a number and the data field is null, the recipe generates an error because a number cannot be compared with null. To prevent this, use the is present condition alongside the less than condition.

Compatible data types

This condition supports string, integer, and number data types.

Examples

Figure: is true

You can also use the is true condition to evaluate formulas. For example, string-type data pills can be converted using string formulas into conditions that return a boolean value.

Compatible data types

This condition is only compatible with boolean data types. You can use this condition to check against a boolean datapill, or check against a formula that evaluates to true or false.

Examples

is not true

The is not true condition defines actions for cases where a boolean data field is false or when a formula evaluates to false. It is the opposite of the is true condition and is essential for workflows that rely on negative or false evaluations.

Figure: is not true

You can also use the is not true condition to check if a formula in the trigger data input field evaluates to false. For example, string-type data pills can be converted into boolean conditions using string formulas, enabling precise evaluations.

Compatible data types

This condition is compatible only with boolean data types. It can be used to evaluate a boolean data pill or a formula that resolves to true or false

is present

The is present condition allows you to define actions based on whether data exists in a specific field. It is essential for workflows that rely on the presence of data rather than its actual value. If the data field is null or an empty string, this condition will not be triggered. It is the opposite of the is not present condition.

Figure: is present

Compatible data types

This condition is compatible with all data types, including integers, floats, dates, and arrays.

Examples

is not present

The is not present condition is used to define actions when a data field is either empty or null. It is essential for workflows that require the absence of data to trigger certain actions. If the field contains any data, this condition will not be activated. It serves as the inverse of the is present condition.

Figure: is not present

Compatible data types

This condition supports all data types, including integers, floats, dates, and arrays.

Examples

#

#

#

#Exampl