RGP + Zapier Integration Event Firing Rules

Read these rules very carefully to understand when the specific Zapier events are triggered, and when they are not triggered.

Customer.created

Fired
 - Customers created via Data Entry -> Add Customer or Data Entry -> Add Family Member
 - Customers created via Find Documents
 - Customers created via Online Transaction Assignment

Not Fired
 - Customers created via import

Customer.contactinfoupdate

Attributes Checked
 - First Name
 - Last Name
 - Middle Name
 - Email
 - Address 1
 - Address 2
 - City
 - State
 - Postal Code
 - Country
 - Home Phone
 - Cell Phone
 - Work Phone
 - Do Not Mail
 - Birthday
 - Barcode

Fired
 - Customer contact info changed via Edit Customer
 - Customer contact info changed via document acceptance in Find Documents
 - Contact contact info changed via online transaction assignment
 - When unsubscribers are downloaded from emails sent via the RGP email system (only impacts Do Not Mail attribute)

Not Fired
 - None

Customer.tag.added

Fired
 - Tags added as part of Data Entry -> Add Customer
 - Tags added as part of customer creation/update in Find Documents
 - Tags added manually in Edit Customer -> Tags
 - Bulk tags added via SINGLE GYM customer query (currently there is 200 event limit per query to prevent runaway triggers - TBD the best approach)

Not fired
 - Bulk tags added via MULTI GYM customer query

Customer.tag.removed

Fired
 - Tags manually removed in Edit Customer -> Tags

Not Fired
 - Tags deleted via bulk action in Data Entry -> Manage Tags

Membership.added

Fired
 - When a membership is configured on a customer in Edit Customer

Not Fired
 - None

Membership.removed

Fired
 - When a membership is removed in Edit Customer (terminate status added or prepaid end dates adjusted)
 - When a membership is automatically terminated by daily maintenance because of prepaid expiration or an existing termination status

Not Fired
 - None

Checkin.created

Fired
 - Check-ins via Check In application
 - Guest pass check-ins

Not Fired
 - None

Invoice.created

Fired
 - For POS invoices
 - For online transaction invoices

Not Fired
 - Dues related invoices

Multigym Considerations

• Triggers are always fired in the context of the gym where the “object” lives.
• Example: in the case of editing a remote customer, the trigger will be fired as part of the remote database’s queue.