--- title: "Training studio: Mindbody sales to webhooks - APIANT.ai" description: "A training studio wanted every new client's first package sale sent from Mindbody to its own systems." canonical: "https://apiant.ai/stories/training-studio-mindbody-sale-webhooks" --- # A training studio wanted every new client's first package sale sent from Mindbody to its own systems. The first live sale went through half an hour after signup. A personal training studio sells its coaching packages in Mindbody, and runs other tools of its own that listen for webhooks. The owner connected Mindbody to APIANT and asked an AI client to build the link. Apps in this story - [ Mindbody](https://apiant.ai/connections/mindbody) ## The challenge When a client bought their first package in Mindbody, the studio's other tools needed to hear about it straight away, with the details attached: who the client is, how to reach them, what they signed, what it costs and how it is paid, and who sold it. A client who already had a package was not news. Later the studio wanted the same for every pricing-option sale. - **30** minutes from signup to the first live sale handled - **14** live sales events from Mindbody, every one handled successfully - **6 forwarded, 8 skipped** each event checked before anything was sent - **3** destinations fed from one sale, all answered At a glance - Business: Personal training studio - Apps: [Mindbody](https://apiant.ai/connections/mindbody), the studio's own webhook receivers - Built with: An AI client, over the [APIANT MCP server](https://apiant.ai/mcp) - Upgraded from free: Day 4 ## The journey - Day 1 ### First package sale, live within half an hour The owner signed up and connected Mindbody about two minutes later. Seven minutes after signup the agent had built the first automation: when Mindbody reports a sale, look up the client's contracts, and only if this is their first one, fetch the package details and send client and package on. It passed its test against real Mindbody data, and six minutes later a live sale ran through it successfully. Live, 30 min after signup - Day 4 ### Upgraded, added a second destination The owner upgraded from free, and within two minutes the agent had built a version that sends each first sale to two receivers instead of one. Its first live sale went to both. Upgraded from free - Day 12 ### Pricing-option sales, and a third destination A second automation for pricing-option sales: it checks the sale type, looks up the client's contact details and posts the sale to two receivers in the studio's own app. The first-contract automation was rebuilt the same session to feed the studio's app as well, three destinations in all. - Days 12 to 16 ### Running Ten live sales events reached the pricing-option automation: three were pricing-option sales and were forwarded, seven were other sale types and were skipped. The first-contract automation forwarded one first sale to all three destinations and skipped one client who already had a contract. Every run succeeded. ## What they built Automation | What it does | Result | First package sale | On a Mindbody sale, checks whether it is the client's first contract; if so, sends client and package details to three receivers | 4 live events across its versions: 3 forwarded, 1 correctly skipped, all successful | Pricing-option sale | On a Mindbody sale, checks the sale type; for pricing options, adds the client's contact details and posts to two receivers | 10 live events: 3 forwarded, 7 correctly skipped, all successful | Two automations live today. The earlier versions were switched off as they were replaced. ## Why it worked - 01 ### It sends only what was asked for. Every event is checked first: a client's first contract, or a pricing-option sale. Eight of the fourteen live events did not qualify and nothing was sent for them. - 02 ### Tested against real Mindbody data. Each version passed a test run before the first live sale reached it. - 03 ### It feeds the systems they already run. The studio kept its existing webhook tools and its own app. APIANT reads Mindbody and hands each sale on, and writes nothing back to Mindbody. ## More stories - [A gym owner wanted ActiveCampaign to know what Mindbody knows. New clients now arrive hourly through the day, tagged with what they actually do.](https://apiant.ai/stories/gym-mindbody-activecampaign-sync) - [A studio owner wanted to see which members were drifting away. He asked his AI client for the Mindbody reports, and had seven working by the next afternoon.](https://apiant.ai/stories/fitness-studio-member-reports) - [A yoga studio wanted every Mindbody sale in its membership register, sorted by its own rules. It went live on day three and sorted 21 paid sales by the afternoon of day four.](https://apiant.ai/stories/yoga-studio-membership-register) ## What would you ask for? [Start free](https://app.apiant.ai/register?utm_source=stories&utm_medium=cta&utm_campaign=story_training)[Read more stories](https://apiant.ai/stories) Details are taken from the account's own run history and shared without the studio's name.