The list below covers all pre-defined conditions in the Automator.
Each condition can access certain data. While there are a number of predefined conditions in the list you can also define a custom condition should you be looking to do something a little more specialised. We are adding new conditions frequently and aim to keep this as up to date as we can but please reach out to support if you see new conditions or have questions about existing).
Creating custom conditions an advanced skill that we encourage you to first experiment with but to not enable the automator until you have someone with expertise check this (when in doubt, email firstname.lastname@example.org).
The unique number that identifies the customer in the system, this can be found at the top of a customer's profile.
Customer First Name
The customer's first name.
Customer Last Name
The customer's last name.
The customer's password - you cannot read a customer's actual password. But instead, this condition is commonly used so that if a customer is registered from the dashboard of CodexFit (i.e. a front of house staff member creates an account but leaves the password empty), you can use this condition with the filter does not equal to effectively use the "send password" reset action. This way, you can have the customer set their own password rather than your team setting one they need to remember or change later.
The customer's email address they used to sign up their account with. This may be commonly used to target automator's to a particular email domain (i.e. the customer's email contains twotwentyseven.com) so you can tailor actions to particular domains.
Customer age (in years)
How many years old the customer is. This is commonly helpful if you want to do things like offer age restricted automatically generated vouchers or maybe add a tag to a customer's account if they are under a certain age.
Customer age (in months)
How many months old the customer is. Same as above but in months. If someone was 30.5 years old, you would put 366 months.
Customer Total Bookings
The total number of bookings made by a customer, this could include multiple bookings for the same event if they have booked more than one spot, say for a friend/buddy. So if a customer booked into an event for themselves and a friend, this condition would return 2.
Customer Total Unique Bookings
The total number of of unique events a customer has booked into. If a customer booked two slot in an event (i.e. for them and a friend), this condition would return 1.
Customer Total Events Attended
The total number of events marked as attended for the customer, this includes any events attended when more than one spot was booked, say for a friend/buddy. This is different from bookings created because it only takes into account actual events the customer was marked as attended at. This tends to be a better metric for milestone actions.
Customer Total Unique Events Attended
The total number of of unique events a customer has attended. Like "Customer Total Unique Bookings" if a customer books two spots in an event for themselves and a friend, this would still only count as 1 unique event attended.
Customers Days Since Last Event Attended
This condition will allow you to send a message or do an action for a customer if something happens and you only want to take the action for customers who were recently active. So maybe rather than giving our a free credit to every customer on their birthday, you only want to give a credit to customers who attended an event within the past 90 days. You could use the event, "Customer's Birthday" but then add this condition with a filter of less than or equal to 90 days in which case the subsequent action would only trigger if a customer had at least one booking in the last 90 days.
Customer Attended Minutes
The duration of attendance in minutes. This is a cumulative count of the number of minutes a customer has spent in class's marked as attended.
Customer Total Video Views
The total number of videos viewed by a customer, this would include if a video has been viewed more than once.
Customer Unique Video Views
The number of unique videos viewed.
Customer Total Video Duration (in seconds)
The total accumulative time, in seconds, a customer has viewed videos for.
Customer Referral Count
This is the number of customer's the referrer has got to successfully follow their link. Please note, only a new customer using the link of an existing customer can count. And this condition purely looks at if a customer has got other customers to register. Please refer to the referral programme setup guide to get more details on this.
Customer Total Points
The total number of points a customer has collected. Customer earn points if you have an automator action setup to give points (which could be built into a referral or loyalty programme).
Customer Total Spend
The customers total overall spend on memberships, credits whether on your website or from the CodexFit admin dashboard and products purchased via the admin dashboard.
Who referred the customer, if they were referred. This is a necessary condition to use in a referral programme so that if someone has followed someone's link and purchased, you need to add this condition and ensure it's value is not empty (i.e., someone did refer them).
The handle of the bundle you have created, this can be found in the bundle information under “handle.”
The unique handle of the plan you have created, this can be found in the plan information under “handle.”
The product stock keeping unit you have added to a product.
The unique ID for each booking created, you can find this in the booking information or on the left hand side on the events booking list.
This is the the name of the subscription once it has been purchased and has been converted from a plan with a recurring payment. The subscription name may not be unique (you must always have a unique plan handle when you setup new plans but sometimes you may reuse the subscription name – this happens sometimes when you start to sell a plan that was similar to one in the past but with an increased cost).
You can also build your own custom conditions to do other things that you may not see in predefined conditions. This is an advanced level feature.
If you are using point pots to reward customers as they earn various points in different pots, the custom condition you will want to use to then trigger an action would be:
customer.point_pots.[name of pot]
Replace name of pot with the pot you setup in the Automator that awards points.
Then imagine you wanted to reward someone when they reached 10 points, you would set it to equals and the value to 10.
If you used the event Customer Purchased, you could then setup a condition to only do something for certain plans. For instance, maybe you only want to send a welcome email to customers purchasing an in studio plan to tell them your terms and conditions for that plan. Your condition would be:
Attribute: Plan Handle
Action: Send email
This would mean the automator would only trigger for customers who purchased that specific plan.
Imagine you want to send an email when customers have attended a certain number of events.
You could setup an automator using the event Booking Attended.
The predefined condition would be:
Attribute: Customer Total Unique Events Attended
Value: (the number of events to reach this milestone)
Action: Send email
This would effectively trigger the action anytime a customer attends the number of events that qualify.
You would like to send a monthly email on successful renewal of subscription once their payment has gone through.
You would use the event Customer Subscription Invoice Paid
Attribute: Subscription Name
Value: (the subscription name this applies to)
Action: Send email
This action would need to be set to no limit to recur monthly with the subscription