04 - New sale (instant) In Mindbody → _zapier

What this automation sends

One message per sale. When a client completes a purchase in Mindbody, you receive a single message with the client, the sale and the total amount paid.

On a multi-item sale, 04 sends a message that the receiving app cannot read, and the sale may not come through at all — with no error shown anywhere, on your side or ours. Your Zap simply never runs for that sale.

04 is reliable for transactions containing a single item. 04B sends one message per item and is not affected, so it handles single-item and multi-item transactions alike. If you are not sure which applies to your business, choose 04B.

What it also does not do: it does not break the sale down item by item. Even where a multi-item message does arrive, it is one message for the whole transaction, not one per 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 occurred.
• 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) – Client’s street address.
• clientCity (string) – Client’s city.
• clientState (string) – Client’s state.
• clientPostalCode (string) – Client’s postal code.
• clientCountry (string) – Client’s country.
• clientBirthDate (string, ISO 8601) – Client’s date of birth.
• clientGender (string) – Client’s gender.
• clientStatus (string) – Client’s status.
• clientAccountBalance (string) – Client’s current account balance.
• clientHomeLocationId (string) – 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) – Any notes associated with the client.

Sale Details

• locationName (string) – Name of the location where the sale occurred.
• appointmentIds (string) – IDs of any associated appointments (if applicable).
• classIds (string) – IDs of any associated classes (if applicable).
• locationId (integer) – ID of the location where the sale was made.
• purchasingClientId (string) – ID of the purchasing client.
• saleDateTime (string, ISO 8601) – Date and time when the sale occurred.
• saleId (integer) – Unique identifier for the sale.
• siteId (integer) – ID of the Mindbody site.
• soldById (integer) – 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

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

Payment Details

• payment_paymentAmountPaid (float) – Amount paid using this payment method.
• payment_paymentGiftCardBarcodeId (string) – Gift card barcode ID used for payment (if applicable).
• payment_paymentId (integer) – Unique identifier for the payment.
• payment_paymentLastFour (string) – Last four digits of the card used (if applicable).
• payment_paymentMethodId (integer) – ID of the payment method used.
• payment_paymentMethodName (string) – Name of the payment method (Cash, Credit Card, etc.).
• payment_paymentNotes (string) – 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