--- title: "Veterans wellness: Mindbody sign-ups into Kit - APIANT.ai" description: "A wellness provider for veterans wanted every Mindbody sign-up in Kit, tagged by who they are and where they go. Four automations were running the same day." canonical: "https://apiant.ai/stories/veterans-wellness-mindbody-kit" --- # A wellness provider for veterans wanted every Mindbody sign-up in Kit, tagged by who they are and where they go. Four automations were running about three hours after the team signed up. The team runs wellness programs for veterans, VA staff and caregivers, at locations in several states. Bookings live in Mindbody, emails go out from Kit. An existing APIANT customer, they signed up for APIANT.ai and asked their own AI client to connect the two. Apps in this story - [ Mindbody](https://apiant.ai/connections/mindbody) - [ Kit](https://apiant.ai/connections/kit) ## The challenge Every new client answers two questions when they sign up in Mindbody: whether they are a veteran, VA staff or a caregiver, and which location they are with. Those answers decide which emails a person should get. But they stayed in Mindbody, and Kit, where the emails are sent from, did not know them. The team wanted each new client in Kit straight away, tagged by program and location. Clients whose location was missing or wrong had to be caught, and a client who confirmed their location should be moved to it in Mindbody as well as in Kit. - **4** automations running about three hours after sign-up - **69** minutes from signing up to the first sign-up running end to end, a team test - **8** Kit tags on the first real client, from one Mindbody sign-up - **1** real new client tagged on the first evening, with nobody at the keyboard At a glance - Business: Wellness programs for veterans, many locations - Apps: [Mindbody](https://apiant.ai/connections/mindbody), [Kit](https://apiant.ai/connections/kit) - Built with: Their own AI client, over the [APIANT MCP server](https://apiant.ai/mcp) - Customer: An existing APIANT customer, new to APIANT.ai that day ## The journey - First 15 minutes ### Signed up, connected both apps Mindbody was connected five minutes after sign-up and Kit ten minutes after that. In between, the team signed in from their AI client. Everything after this was built from there. - At 27 minutes ### New memberships into Kit The first automation: when a client is given a membership in one of the programs, add them to Kit. It passed three test runs and was switched on at 40 minutes. - At 46 minutes ### Every new client, tagged by who they are and where they go The second automation listens for new clients in Mindbody, reads their answers to the two sign-up questions, and adds them to Kit with the matching program and location tags, plus their marketing tags when they have opted in. At 69 minutes the team signed up a test client in Mindbody, and it arrived in Kit, tagged. First sign-up through, 69 min after sign-up - At about 1 hour 25 ### A weekly check The third automation runs every Monday morning: it looks at the week's changed clients in Mindbody and adds the matching location tag in Kit for each of them. - At about 1 hour 35 ### Refined, and the gaps caught The team kept asking for changes while it ran. Clients who answered that their location was not listed now get a "location needed" tag, so someone can follow up. - By about 3 hours ### Clients confirm their own location The fourth automation takes a client's answer from a location form, moves their membership to that location in Mindbody, tags them in Kit, and flags the change for the team to check. It passed its final test run and was switched on about three hours after sign-up. Four automations running - That evening ### Running on its own The first real client signed up in Mindbody, about four and a half hours after the team did. They were tagged in Kit with eight tags, program, location and marketing among them, with nobody at the keyboard. ## What they built Automation | What it does | Result | New client into Kit | On a new Mindbody client, reads the sign-up answers and adds the client to Kit with program, location and marketing tags; tags clients whose location is not listed | 1 real client and 1 team test on the first evening, both successful | New membership into Kit | On a new Mindbody membership in a second program, adds the client to Kit | Running, passed its tests | Weekly location check | Every Monday, adds Kit's location tag for each client changed in Mindbody that week | Passed its test; first scheduled run on the first Monday | Location form | Moves a client's membership to the location they confirm, tags them in Kit and flags the change for the team | Running, passed its final test | Results as of the first evening. A fifth, run-by-hand automation was used once to catch up earlier clients. ## Why it worked - 01 ### It uses the answers they already collect. No new sign-up form, no new fields to fill. The two questions every client already answers in Mindbody now drive the tags in Kit. - 02 ### Each one tested before it went on. Each of the four passed a test run against their real Mindbody and Kit accounts before it was switched on. - 03 ### No dashboard to learn. Each automation, and each change, was built from the AI client they already use. ## 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 training studio wanted every new client's first package sale sent from Mindbody to its own systems.](https://apiant.ai/stories/training-studio-mindbody-sale-webhooks) - [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_veterans)[Read more stories](https://apiant.ai/stories) Details are taken from the account's own run history and shared without the provider's name.