Wix Automations: Best Practices for Creating Conditions

Conditions allow you to set and manage complex automation flows.

For example, you use Wix Restaurants and have introduced a new menu for tables of 4 guests and over. You'd like to send an email update to all customers who have made such bookings. By creating an email automation with the condition that a reservation is for a party size greater than 3, you're targeting this group of customers and not customers who have booked tables for smaller groups.

For conditions to work effectively, they must be set up properly. Key to this is selecting the correct "operator" (e.g. "is greater than", "contains") and using it logically. Follow the best practices below as you add conditions to your automations.

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".

The example below (If: Contact email is "a pending site member" or If: Contact email is "a site member") is not going to work correctly because the text strings "a pending site member" and "a site member" will never appear in the contact email field.

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 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.

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.

The example below (If: Booking creation date is true) is not going to apply a condition because there will always be a value (there will always be a "true") if a booking has been created.