04C - New sale itemized payment (instant) In Mindbody → _zapier

What this automation sends

One message per payment method used. If a client pays part in cash and part by card, you receive two messages, one for each payment.

Use this when you need to know how the client paid.

What it does not do: it does not break the sale down by item. For that, use 04B — New Sale Line Item.

Payload Structure

Root Object

• eventId (string) – Identifies the event type (clientSale.created).
• eventInstanceOrigin (string) – Source identifier for the event.
• eventInstanceOriginationDateTime (string, ISO 8601) – Timestamp when the sale was recorded.
• eventSchemaVersion (integer) – Version of the event schema.
• messageId (string) – Unique identifier for the message.

Client Details

• clientId (string) – Internal Mindbody client ID.
• clientFirstName (string) – Client’s first name.
• clientLastName (string) – Client’s last name.
• clientEmail (string) – Client’s email address.
• clientPhone (string) – Client’s phone number.
• clientAddressLine1 (string or null) – Client’s street address.
• clientCity (string or null) – Client’s city.
• clientState (string) – Client’s state.
• clientPostalCode (string or null) – Client’s postal code.
• clientCountry (string) – Client’s country.
• clientBirthDate (string or null, ISO 8601) – Client’s date of birth.
• clientGender (string) – Client’s gender.
• clientStatus (string) – Client’s status (Non-Member, Member, etc.).
• clientAccountBalance (string) – Client’s current account balance.
• clientHomeLocationId (string or null) – ID of the client’s home location.
• clientSalesRepFirstName (string) – First name of the assigned sales representative.
• clientSalesRepLastName (string) – Last name of the assigned sales representative.
• clientSalesRepId (string) – ID of the assigned sales representative.
• clientNotes (string or null) – Any notes associated with the client.

Sale Details

• locationName (string) – Name of the location where the sale was recorded.
• locationId (integer) – ID of the location where the sale was made.
• appointmentIds (string) – IDs of any associated appointments (if applicable).
• classIds (string) – IDs of any associated classes (if applicable).
• purchasingClientId (string) – ID of the purchasing client.
• saleDateTime (string, ISO 8601) – Date and time when the sale was recorded.
• saleId (string) – Unique identifier for the sale.
• siteId (string) – ID of the Mindbody site.
• soldById (string) – ID of the staff member who processed the sale.
• soldByName (string) – Name of the staff member who processed the sale.
• totalAmountPaid (float) – Total amount paid for the transaction.

Item Details (If Available)

• item_amountDiscounted (float or null) – Discount applied to the item.
• item_amountPaid (float or null) – Amount paid for the item.
• item_giftCardBarcodeId (string or null) – Gift card barcode ID (if applicable).
• item_itemId (string or null) – ID of the purchased item.
• item_name (string) – Name of the purchased item.
• item_paymentReferenceId (string or null) – Payment reference ID associated with the item.
• item_quantity (integer or null) – Quantity of the item purchased.
• item_recipientClientId (string or null) – Client ID of the item recipient.
• item_type (string) – Type of item (Service, Product, Contract, etc.).

Payment Details (If Available)

• payment_paymentAmountPaid (float or null) – Amount paid using this payment method.
• payment_paymentGiftCardBarcodeId (string or null) – Gift card barcode ID used for payment (if applicable).
• payment_paymentId (string or null) – Unique identifier for the payment.
• payment_paymentLastFour (string or null) – Last four digits of the card used (if applicable).
• payment_paymentMethodId (string or null) – ID of the payment method used.
• payment_paymentMethodName (string) – Name of the payment method (Cash, Credit Card, etc.).
• payment_paymentNotes (string or null) – Notes associated with the payment.

Summary

This event ensures that new sales transactions in Mindbody are instantly updated in Zapier-powered workflows, allowing businesses to automate tracking, reporting, and customer engagement efficiently.

---

v1.4 Field Reference

Version: 1.4 | Status: Fixed | Total fields: 47

What's New in v1.4

• Client Enrichment (19 fields): clientId, clientFirstName, clientLastName, clientEmail, clientPhone, clientUniqueId, clientAddressLine1, clientCity, clientState, clientPostalCode, clientCountry, clientBirthDate, clientGender, clientRedAlert, clientStatus, clientAccountBalance, clientHomeLocationId, homeStudioName, clientSalesRepFirstName, clientSalesRepLastName, clientSalesRepId, clientNotes, clientYellowAlert, clientFirstClassDate, clientWorkExtension
• Location (1 field): locationName
• Client-prefixed naming. All client fields are enrichment (sale trigger only has purchasingClientId)
• Metadata from trigger

Complete Field List