A Trigger is the event that starts a Zap i.e. when a customer profile is created, or a membership is purchased. Once you've set up a Zap, Zapier will monitor for that trigger event in your TeamUp account.

At launch, we have created 6 triggers which we will explain below. We’re always keen to learn about new requirements, so please let us know if there’s anything else that would be helpful.

Trigger 1: Customer Updated

Customer updated is sent to Zapier when something changes on a customer profile. This could include:

  • Email address or name
  • A field, for example an answer to an injury question
  • Something else

The data sent to from TeamUp to Zapier when this happens includes:

  • First name
  • Last name
  • Profile fields including emergency contacts, address and any other custom fields you created using the TeamUp Customer Fields feature and are collected on a Form.
  • URL for their profile photo
  • Email
  • Other TeamUp specific data like profile ID number

Trigger 2: Customer Created

Customer Created is very similar to Customer Updated with the exception that it just runs once when a customer is created. The set of data that is sent also similarly includes:

  • First name
  • Last name
  • Profile fields including emergency contacts, address and any other custom fields you created using the TeamUp Customer Fields feature and are collected on a Form.
  • URL for their profile photo
  • Email
  • Other TeamUp specific data like profile ID number

Trigger 3: Customer Membership Created

Customer Membership Created runs when a new membership is purchased by a customer, or added from the business account. It includes the following set of data:

  • Name and description of the membership
  • Expiration date
  • Recurring billing schedule and description
  • Start date
  • Customer profile fields including name and email
  • Dates and usage summary
  • Other TeamUp data including membership ID

Trigger 4: Customer Membership Started

Customer Membership Started runs when a customer membership starts. 

You can decide in Zapier if your Zap should pick up a customer membership purchase with a start date set in the past.

Similarly to Customer Membership Created, it includes the following set of data:

  • Name and description of the membership
  • Start date
  • Expiration date
  • Recurring billing schedule and description
  • Customer profile fields including name and email
  • Dates and usage summary
  • Other TeamUp data including membership ID

Trigger 5: Customer Membership Ended

Customer Membership Ended runs when a customer membership ends due to the expiration date being reached. 

Note. this will be triggered for packs on either the expiration date or the date of the last class it was used for, whichever comes first.

Similarly to the other membership triggers, it includes the following set of data:

  • Name and description of the membership
  • Start date
  • Expiration date
  • Recurring billing schedule and description
  • Customer profile fields including name and email
  • Dates and usage summary
  • Other TeamUp data including membership ID

Trigger 6: Customer Membership Cancelled

Customer Membership Cancelled runs when a customer membership is cancelled. This is sent when a user clicks the “cancel” button for a recurring membership. Similarly to the other membership triggers, the following set of data is included:

Similarly to the other membership triggers, it includes the following set of data:

  • Name and description of the membership
  • Start date
  • Expiration date
  • Recurring billing schedule and description
  • Customer profile fields including name and email
  • Dates and usage summary
  • Other TeamUp data including membership ID
Did this answer your question?