Wix Automations: Adding and Setting Up Conditions

Conditions add flexibility to automations by letting you set specific rules for what happens next. This means your automation can branch in different directions based on what your site or contacts do. For example, you can have the automation send an email only if the customer spends over $100.

Adding a condition

Adding a condition gives you control over the next steps in your automation, using details that Wix collects each time it runs. You set the criteria that matter most to you, so actions only happen when your chosen rules are met.

• In the THEN path, the automation flow continues only if the condition is met.

• In the ELSE path, you can define what happens if the condition isn’t met.

To add a condition:

1. Create a new automation or edit an existing automation.

2. Click the Add Step icon

   

   .

3. Click Condition.

4. Choose how you want to set up your condition:

Basic logic

1. Click the Basic logic tab.

2. Click the Select a property drop-down and choose the dynamic field that the automation collects when it runs (e.g. Party Size).

   Tip: Learn more about the property picker and all that it offers.

3. Click the Select logic drop-down and choose an operator that will compare the received data with the value (e.g. 'is greater than').

4. Click the Enter value drop-down or text box that appears to set the right value (e.g. 3). Tip: Click Customize to create custom workflows using the formula field.

5. (Optional) To add any additional criteria, click +And/+Or to choose the relationship between your criteria.

6. Click the If this condition isn't met drop-down and choose:

   • End flow: No action will take place if the condition isn't met.

   • Follow Else path: Click the + to add a step under the new path that appears in your automation that will occur when the condition isn't met.

Custom code

1. Click the Custom code tab.

2. Choose how to create your custom code:

   • Click Edit Code to write your own Java code condition.

   • Click Code with AI to write a prompt that describes what you want the condition to check and click Generate code.

3. Click Save once you're happy with how the code is written.

Building a condition with the property picker

In the below example, we'll use the property picker to set up the condition: check if an order's payment status is equal to 'Paid' before continuing with the automation.

To build a condition with the property picker:

1. Create an automation in the new automation builder.

2. Click the Add Step icon

   

   .

3. Click Condition.

4. Click the Basic logic tab.

5. Click the Select a property field to open the property picker.

6. Choose the property you want the condition to check from the nestable list. For our example, we want the condition to check Payment status.

Tip:

Hover over a property to see additional information such as the property type and an example of how to use it in your automation.

1. Click the Select logic dropdown and choose the logic from the available data types. For our example, we want to choose the type is exactly.

1. Finally, choose the resulting output the condition should check. For our example, we want the condition to check that the text is exactly the word Paid so we enter the word 'Paid' into the text field.

1. Click Apply to save the condition.

2. Continue with the rest of the automation flow including choosing an action. In our example, we added an action 'Give Loyalty Points'.

Now, when an order is placed, the condition checks if the payment status is 'Paid' before continuing with the flow.

Tip:

You can build an Else path if you want the automation to do something different if the condition is not met. In our example, if the order is not paid, send an email reminder to pay the order.

Building the logic of a condition

For conditions to work effectively, make sure to select the correct operator (e.g. "is greater than", "contains") and follow the best practices described in this article.

Click an option below to learn more about an operator:

Text operators:

Text operators are used for comparing names, labels, etc.

Best practice: Use text operators for properties that are text strings, for example when a restaurant name is exactly "Paulie's Pizza".

Number operators

Number operators are used for comparing any numerical property, like quantities.

Best practice: Use number operators for properties that will always be numbers, for example sending an email when a reservation party size is greater than 10.

Date and time operators

Date and time operators are used for comparing date and time properties to specific dates and times.

Best practice: Use date and time operators when you're basing a condition on an exact date or time, for example contacting all customers who made a purchase this month.

Array (list) operators

Array operators are used to specify a list of multiple values or objects, instead of selecting just one.

Best practice: Use array operators when you're including a specific list of products in your automation, for example shirts sold in your store.

True/false operators

True/false operators are used for comparing any boolean properties that will always be true or false.

Best practice: Use true/false operators for properties that will always be one of two states, for example a checkbox that is ticked or unticked.