> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/your-data-sources/mindbody.md).

# Mindbody

![Mindbody](/files/9RwqaiGB7amcS8ClDkvD)

Mindbody brings the core of your studio — **clients, memberships, classes, attendance, and sales** — into Kula Intelligence.

## What we read — and what we don't

* **We read:** your clients and memberships, classes and class visits (attendance), sales, staff, and locations — read-only.
* **We don't:** book, cancel, charge, or change anything in Mindbody.

## What you'll need

* Your Mindbody **Site ID**.
* A **staff username and password** with read access. (Kula holds the Mindbody developer key; you provide your own staff login.)
* You may need to **activate the Kula integration** in your Mindbody account the first time.

## How to connect

1. In Kula, open **Connectors → Mindbody** and enter your Site ID and staff login, then click **Test**.
2. If Mindbody asks you to **activate the integration**, approve it in your Mindbody account and click **Test** again.
3. Click **Connect**, then start the **import**. Your history pulls in the background — the busiest parts (class visits and sales) are imported in chunks, oldest first.
4. When the import finishes, click **Process** to turn it into the tidy members, attendance, and sales the AI reads.

## Good to know

* A busy studio's first import is the slowest part of setup — class attendance especially. It runs in the background and **resumes where it left off** if it's interrupted, so you can close the tab.
* Re-running the import only fills gaps; **Process** is safe to repeat.

## If it stops working

The usual cause is a changed staff password or a deactivated integration. Update the login (or re-activate the integration) and re-test. See [Keeping your connectors healthy](/your-data-sources/operating.md).