APIANT.ai / Stories / Fitness studio
Customer story · Fitness studio · Mindbody, GoHighLevel and Kisi
A fitness studio wanted each new Mindbody membership or recovery pass to start its GoHighLevel follow-up and Kisi door access. Both were built in one day.
A fitness studio sells memberships and recovery passes in Mindbody, runs its welcome and follow-up in GoHighLevel, and opens its doors through Kisi. The owner asked an AI client to join the three: when someone signs up, hand them on and give them access.
Apps in this story
The challenge
The studio sells memberships and recovery passes in Mindbody. Its welcome and follow-up run in GoHighLevel, and its doors open through Kisi. It needed each new membership or recovery pass to reach both, the moment it happens: the buyer handed to the right GoHighLevel workflow for what they signed up for, and placed in the right access group in Kisi.
- 29new memberships and recovery passes handed to GoHighLevel in six days
- 17of them checked in Kisi, each buyer placed in or already in the right access group
- One dayto build the GoHighLevel hand-off and the Kisi door access
- Under a secondaverage run time on APIANT per new contract
The journey
-
Day 22, morning
Recovery passes into GoHighLevel
The first ask: when a client buys a recovery pass in Mindbody, send them to the GoHighLevel workflow the studio runs for that offer. The agent built it on Mindbody's instant new-contract event, and its test passed two minutes later. The first live recovery pass went through about two and a half hours after that.
-
Day 22, afternoon
Memberships too
A second automation for new memberships, leaving recovery passes to the first. Its first live membership went through a little over an hour after it was built.
-
Day 22, evening
Door access in Kisi
Next, the doors. The agent built a Kisi connector for the account, with three operations: find a person by email, create a person, add a person to a group. Ten minutes later both automations had a new branch: find the buyer in Kisi, create them if they are not there, and add them to the members group or the recovery group.
-
Days 22 to 27
Every new contract handed on
Twenty-six recovery passes and three memberships handed to GoHighLevel. Once the Kisi branch was in, seventeen of them were checked in Kisi, each buyer placed in or already in the right access group.
29 handed on
What they built
| Automation | What it does | Result, days 22 to 27 |
|---|---|---|
| Recovery pass | On each new Mindbody contract, checks for a recovery pass; hands the buyer to the GoHighLevel recovery workflow; finds or creates the buyer in Kisi and adds them to the recovery group | 26 recovery passes handed on, 3 membership contracts left alone; 15 checked in Kisi |
| Membership | On each new Mindbody contract, leaves recovery passes to the other automation; hands the buyer to the GoHighLevel new-member workflow; finds or creates the buyer in Kisi and adds them to the members group | 3 memberships handed on, 15 recovery passes left to the other automation; 2 checked in Kisi |
Two automations from a larger account; this story covers the new-contract hand-off only.
Why it worked
- 01
It acts the moment someone signs up.
Both automations start on Mindbody's own event for a new contract, not on a schedule, and a run takes under a second on APIANT on average.
- 02
It feeds the systems the studio already runs.
The welcome and follow-up stay in the studio's own GoHighLevel workflows, and access stays in Kisi. APIANT reads the new contract and hands it on, and writes nothing back to Mindbody.
- 03
A missing connector was part of the job.
Kisi needed three operations the account did not have yet. The agent built them, and ten minutes later both automations carried the Kisi branch.
More stories
- 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 dental practice asked for its online bookings and health forms to land in Cliniko, matched to the right patient or not written at all.
- A church needed each Stripe gift in DonorPerfect, on the right donor, with its own codes. By the next day, its charges were arriving as gifts on their own.
What would you ask for?
Details are taken from the account's own run history and shared without the studio's name. No client, sale or contract details are included.