Conditions ​

Create IF conditions in your Workato recipes by defining three key components: a Data field, a Condition, and a Value. The Data field is the variable data from your app, for example, case status, or lead rating. The Value is the static value you plan to check against, such as Closed or Hot. Data fields and values are case sensitive.

This section covers fourteen available conditions, with trigger conditions as examples. You can also combine multiple conditions with the AND or OR operators to create complex logic.

Each condition is compatible with different data types. Using a condition with an invalid data type may prevent the recipe from starting or functioning correctly.

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

• Throw a trigger error after starting, preventing it from picking up trigger events.
• Filter out all trigger events.

Where conditions can be used ​

You can use conditions in the following features to refine your workflow:

• IF control statements: Use conditions within IF control statements to execute specific steps or actions based on your data.

• While loop: Create conditions within a repeat while loop to repeat actions until a specific condition is met.

• Trigger conditions: Set trigger conditions to filter which trigger events are processed by the recipe, ensuring only relevant events are picked up.

contains ​

The contains condition allows you to check if a data field contains a specified value within a sequence of conditional checks. This approach is useful when you must route or process data differently based on the presence of specific content. This condition is the inverse of the doesn't contain condition and is case-sensitive. You can adjust the case of both the data and value for case-insensitive comparisons as required.

The control statement processes new Google Calendar events only if the event Summary contains the word Review.

Compatible data types ​

This condition is compatible with array and string data types.

Examples ​

starts with ​

The starts with condition allows you to check if a data field string begins with a specified value in a sequence of conditions. This condition is the inverse of the doesn't start with condition and is case-sensitive. Verify that both the data and the value are in the same case (either lowercase or uppercase) to ensure accurate comparisons.

The control statement processes new Zendesk users whose phone numbers start with (810) or (749).

The starts with condition matches exact strings only, and does not recognize null values.

Compatible data types ​

This condition is only compatible with string data types.

Examples ​

Special non-string data type cases ​

Avoid comparing non-string data types using the starts with condition to prevent trigger errors. For example, comparing two number types directly results in an error.

Trigger errors occur when comparing number types with the starts with condition.

In situations where the data field is a non-string datapill and the comparison value is a string, Workato automatically converts the datapill's value to a string for the comparison. The comparison evaluates to true if this converted value meets the condition.

Non-string datapills are converted to a string for comparison if the value is a string

ends with ​

The ends with condition allows you to check if a data field ends with a specific value. This condition is the inverse of the doesn't end with condition and is case-sensitive. Verify that both the data and the value are in the same case (either lowercase or uppercase) to ensure accurate comparisons.

The control statement filters Gmail messages from senders whose email address ends with @partnercompany.com.

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

Compatible data types ​

This condition is only compatible with string data types.

Examples ​

Special non-string data type cases ​

Avoid comparing non-string data types using the ends with condition to prevent trigger errors. For example, comparing two number types directly results in an error.

Trigger errors occur when comparing number types with the ends with condition.

In situations where the data field is a non-string datapill and the comparison value is a string, Workato automatically converts the datapill's value to a string for the comparison. The comparison evaluates to true if this converted value meets the condition.

Non-string datapills are converted to a string for comparison if the value is a string.

does not contain ​

The doesn't contain condition allows you to define actions when specific values are absent in your data fields. This condition is the inverse of the contains condition and is case-sensitive. Verify that both the data and the value are in the same case (either lowercase or uppercase) to ensure accurate comparisons.

The control statement filters emails whose subjects do not contain Meeting reminder.

Compatible data types ​

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

Examples ​

does not start with ​

The doesn't start with condition allows you to define actions when specific starting sequences are absent in your data fields. This condition is the inverse of the starts with condition and is case-sensitive. Verify that both the data and the value are in the same case (either lowercase or uppercase) to ensure accurate comparisons.

The control statement in the recipe processes Jira issues where the status category does not start with In Review.

Compatible data types ​

This condition is only compatible with string data types.

Examples ​

Special non-string data type cases ​

Avoid comparing non-string data types using the doesn't start with condition to prevent trigger errors. For example, comparing two number types directly results in an error.

Trigger errors occur when comparing number types with the doesn't start with condition.

In situations where the data field is a non-string datapill and the comparison value is a string, Workato automatically converts the datapill's value to a string for the comparison. The comparison evaluates to true if this converted value meets the condition.

Non-string datapills are converted to a string for comparison if the value is a string.

If your trigger data is nil (or null), Workato does not pick up the trigger event, even if it technically meets the condition. For example, nil doesn't start with 345.

does not end with ​

The doesn't end with condition allows you to define actions for data fields that do not end with a specified value, following an initial IF condition. This is the inverse of the ends with condition and is case-sensitive. Verify that both the data and the value are in the same case (either lowercase or uppercase) to ensure accurate comparisons.

The control statement filters DocuSign documents whose titles do not end with Contract.

Compatible data types ​

This condition is only compatible with string data types.

Examples ​

Special non-string data type cases ​

Avoid comparing non-string data types using the doesn't end with condition to prevent trigger errors. For example, comparing two number types directly results in an error.

Trigger errors occur when comparing number types with the doesn't end with condition.

In situations where the data field is a non-string datapill and the comparison value is a string, Workato automatically converts the datapill's value to a string for the comparison. The comparison evaluates to true if this converted value meets the condition.

Non-string datapills are converted to a string for comparison if the value is a string.

If your trigger data is nil (or null), Workato does not pick up the trigger event, even if it technically meets the condition. For example, nil doesn't end with 345.

equals ​

The equals condition allows you to define actions for situations when a data field exactly matches a given value. This condition is crucial for processes that depend on exact matches. This condition is the inverse of the does not equal condition and is case-sensitive. Verify that both the data and the value are in the same case (either lowercase or uppercase) to ensure accurate comparisons.

The control statement in the recipe processes new Okta events if the Credential type equals External..

Compatible data types ​

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

Examples ​

Special cases ​

Workato converts strings to float data types for comparisons with numeric values. When comparing a number and a string, if the string can be a float, Workato treats it as such for the comparison.

Floats have limited precision. Comparisons 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 a 0123 to 83.

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

does not equal ​

The does not equal condition allows you to define actions for cases when a data field does not exactly match a specified value. This condition is crucial for identifying discrepancies or variations in data. This condition is the inverse of the equals condition and is case-sensitive. Verify that both the data and the value are in the same case (either lowercase or uppercase) to ensure accurate comparisons.

The control statement in the recipe processes new Zendesk tickets only when their Priority does not equal Low. This approach focuses on tickets with higher priority levels for immediate action.

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 allows you to define actions for when a data field's value exceeds a specified number or date. This is particularly effective for prioritizing tasks or records based on numerical or date criteria. This condition is the inverse of the less than condition.

The control statement in the recipe processes new Salesforce accounts only if their SLA Expiration Date is greater than 12/21/2024. This approach ensures prioritization of accounts based on the urgency of their service agreements.

If value is set to a number and the data field is null, the recipe raises an error as a number cannot be compared with null. To address this, use an is present condition along with the greater than condition for reliable results.

In addition to the ELSE IF condition, adding an is present condition ensures the recipe processes new Salesforce opportunities with an existing (non-null) SLA expiration field that is set to expire after 12/21/2024.

Compatible data types ​

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

Examples ​

less than ​

The less than condition allows you to define actions for when a data field's value is lower than a specified threshold, following an initial IF condition. This is essential for scenarios where ranking or filtering is based on lower numerical or date values. This condition is the inverse of the greater than condition.

The control statement is applied to new Shopify product variants, processing only those whose variant Price is less than 50.

If the value is a number and the data field is null, the recipe throws an error, as you cannot compare a number with null. To resolve this, combine an is present condition with the less than condition.

Compatible data types ​

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

Examples ​

is true ​

The is true condition allows you to define actions for cases when a boolean data field is true, or when a formula evaluates to true. This condition is crucial for making decisions based on binary data or specific formula outcomes. This condition is the inverse of the is not true condition.

The control statement processes new Shopify product variants only if the variant's Requires shipping field is marked as true.

Additionally, you can use the is true condition to assess formulas. For example, you can convert string type datapills through string formulas into conditions that evaluate to a boolean.

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 allows you to define actions for when a boolean data field is not true or when a formula evaluation results to false. This is the inverse of the is true condition and is crucial for workflows that depend on negative or false evaluations.

The control statement processes new Google Calendar events only when the Guests can modify option is not set to true. This ensures the recipe selectively targets events where guests have restricted modification rights.

Additionally, you can use the is not true condition to verify if a formula in the trigger data input field results in false. For example, you can convert string type datapills into boolean conditions using string formulas, allowing for precise evaluations.

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 present ​

The is present condition allows you to define actions based on the presence of data in a specific field. This condition is crucial for workflows that respond to the presence of data rather than its value. If the data field is null or an empty string, the condition does not trigger. This condition is the inverse of the is not present condition.

The control statement processes new Box files only when a file Name is present. This is particularly useful for ensuring that only files with names are considered for further actions in the recipe.

Compatible data types ​

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

Examples ​

is not present ​

The is not present condition allows you to define actions for when a data field is empty or null. This condition is essential for workflows that rely on the absence of data to trigger specific actions. The condition does not activate if there is data present in the field. This condition is the inverse of the is present.

The control statement processes new Zendesk tickets only if no Ticket form ID is assigned to them.

Compatible data types ​

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

Examples ​