Automation Events

Automation events are steps within an automation that allow your clients to skip ahead through other steps and jump right to the event step when they take a specific action.

For example, let's say you have an automation with an email sequence of 5 emails prompting your clients to purchase a membership. If after the second email, your client purchases a membership, you'd want to skip sending the remaining emails. By adding an event step below the email sequence, this client will jump right to the event step and will not receive the remaining 3 emails.

Default behavior vs. Pause and Wait

By default, event steps work as jump-ahead points — contacts don't stop at the event step. Instead, if the event occurs while the contact is on an earlier step, they skip forward to the event step and continue from there.

If you want a contact to stop and wait at the event step until the event happens, enable the "Wait her for this event" toggle. When enabled:

• Contacts will pause at this step when they reach it.
• They remain here until the selected event occurs.
• Once the event occurs, they continue to the next step in the automation.

Available events

Registers for an Event/Series

This event will bring any client that registers for an event or series to this step. You can filter this down to clients who register for a specific offering, event series, or a specific event.

Registers for an Appointment

This event will bring any client that registers for an appointment to this event step. You can filter this down to an appointment for a specific offering or a specific staff member.

Purchases a Package or Membership

This event will bring any client who purchases a package or membership to this event step. You can filter this down to just packages or memberships or even specific packages or memberships.

Purchases a Store Item

This event will bring any client who purchases a store item to this event step. You can filter this down to store items from specific store sections, by type (digital or physical goods), or a specific store item.

A Contact Tag is Added

This event will bring any client who has a specific contact tag added to them to this event step. This tag can be added by you manually, or the tag can be assigned to them automatically by signing up using the newsletter signup form on a custom page, or one of the tags automatically assigned when the client performs an action. A contact tag can also be added via an automation action.

A Contact Tag is Removed

This event will bring any client who has a specific contact tag removed from them to this event step. This tag can be removed by you manually, or through another automation action.

A Custom Field Value is Changed

This event will bring a contact whose custom data field is changed to this event step. 

A Contact Subscribed to Your Newsletter

This event will bring a client to this event step as soon as they subscribe to your newsletter. This could be through one of your newsletter signup forms or by opting in when signing up for one of your classes, booking an appointment, or making a purchase.

A Membership is Cancelled

Fires when a client's membership is cancelled. You can filter this down to a specific membership.

Uses a Package or Membership

Fires when a client uses a session from a package or membership. You can filter this down to specific packages or memberships.

A Membership is Paused

Fires when a client's membership is paused. You can filter this down to a specific membership.

A Membership is Changed

Fires when a client's membership is changed (for example, switching from one membership plan to another). You can filter this down to a specific membership.

A Contact Enters a Contact Journey Lane

Fires when a contact enters a contact journey lane. You can filter this down to a specific lane.

A Contact Exits a Contact Journey Lane

Fires when a contact exits a contact journey lane. You can filter this down to a specific lane.

Additional Notes

When evaluating whether a client can jump to an event step, the system checks to see if there is a valid path from where the client currently is to the event step.

 

In the example above, if the client is at Step 1, and the event "A contact tag is added" (Step 3) occurs, the client will jump from Step 1 to Step 3 as there is a valid path from 1 to 3. If the client was at Step 2, there is still a valid path to Step 3, and the client can jump from 2 to 3.

However, if the client is at Step 4 (below), and the event occurs, nothing will happen as there isn't a valid path from Step 4 back to Step 3.

Tip: If you need contacts to wait at a specific point for an event, choose "Wait here for the event" mode. This ensures contacts stop at the event step and don't pass through it.

To learn more about automations, be sure to check out our overview help article or view the other articles on this feature.