The list below covers all events in the Automator.
Each event can access certain data in the conditions.
In each event below, you will see the title of the event on the first line followed by the data/resources that the event gives you access to. This is important because not all events get access to all data.
You'll see the name of the event followed by what resources it can see.
Events and Data/Resources Accessible
CustomerRegistered
customer, referrer
CustomerPurchased
customer, referrer
CustomerSubscriptionInvoicePaid
plan, subscription, customer, referrer
CustomerVideoView
viewing, video, customer, referrer
CustomerBirthday
customer, referrer
CustomerDeleted
customer, referrer
CustomerUpdated
customer, referrer
CustomerPurchasedBundle
bundle, customer, order_line
CustomerPurchasedProduct
customer, product_variant, referrer
CustomerPurchasedSubscription
plan, customer, referrer
CustomerEarnedPoints
customer, referrer
CustomerReferralCount
customer, referrer
BookingCreated
booking, event, customer, referrer
BookingAttended
booking, event, customer, referrer
BookingCancelled
booking, event, customer, referrer
SubscriptionCancelled
plan, subscription, customer, referrer
WaitlistConverted
customer, event, waitlist, referrer
InvoicePaid
invoice, customer, order_lines
Example 1
If you used the event Customer Registered, you could then setup a condition to only do something for certain customers with data that is available about a customer. For instance, maybe you only want to send a welcome email to customers with an email address that contains a certain domain. Your condition could be:
Custom Condition: customer.email
Contains
twotwentyseven.com
This would mean the automator would only trigger for customer's whose email contained twotwentyseven.com.
Example 2
Imagine you want to send an email when customers have attended a certain event type.
You could setup an automator using the event Booking Attended.
Then you could create a custom condition which could be:
Customer Condition: booking.event.event_type.handle
Equals
ride-45
This would effectively trigger the action anytime a customer attended an event which event type handle was ride-45.