Wix Automations: Understanding Conditions Operators
This article refers to the previous automation builder. If you're not seeing this version, read our article about the new version of the automation builder.Conditions allow you to set and manage complex automation flows.For conditions to work effectively, they must be set up properly. The 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.In this article, learn more about conditions that use:
Text operators Number operators Date and time operators Array (list) operators True/false operatorsText operatorsText 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".See an exampleDrew wants to give a 10% discount on the next purchase for those who fill out her feedback survey. Drew creates an automation to send a coupon when a form is submitted. To ensure that a coupon is sent only when her Survey 2024 form is submitted, she added a text operator condition to specifying that survey.Number operatorsNumber 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.See an exampleBenjie is introducing a chef's menu for tables of 5 guests and over. He wants to send an email update to all customers who have made such bookings. To help, Benjie sets up an automation with a number operator condition ensuring that an email is sent only to groups with a party size of 5 or greater. Date and time operatorsDate 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.See an exampleDebbie owns a yoga studio. She wants to send a special thank you email to all her clients who book a session at her studio on New Years encouraging them to start the year off right. To help feel confident that her email will reach the right clients, she creates a condition using the date & time of when a client booked their session.
Array (list) operatorsArray 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.See an exampleSophie got new soaps in her inventory. She wants to include a '20% off your next purchase' coupon with every purchase of her new soaps. Sophie sets up an array condition to ensure that the email gets sent to the right customers. True/false operatorsTrue/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.See an exampleJosh is launching his newsletter. He wants to add a label to every subscriber contact who opts into receiving the newsletter. To help him, Josh uses a true/false condition in his automation to include only those who have clicked the checkbox to signed up for the newsletter.Looking for more capabilities?Currently, it is not possible to add a condition with more complexity than an "if" condition. Vote for the ability to add an "else" condition, create a multipath automation or add a condition that uses a customer's interaction to impact an automation's flow.