> 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/connectors.md).

# How connectors work

A **connector** brings your studio's data from a tool you already use into Kula Intelligence, so the AI can answer questions about it. You connect each source once; after that it keeps itself up to date.

Each source has its **own setup** (where to find a key, which sign-in to use) and its **own rules** for what we're allowed to read — those live on the per-source pages below. But they all **operate the same way**, and that shared part — gaps, outages, recovery — is on one page: [Keeping your connectors healthy](/your-data-sources/operating.md).

## What you can connect

| Source                                          | Brings in                                               |
| ----------------------------------------------- | ------------------------------------------------------- |
| [Stripe](/your-data-sources/stripe.md)          | Payments, subscriptions, invoices                       |
| [Wix](/your-data-sources/wix.md)                | Bookings, members, pricing plans, online store          |
| [Mindbody](/your-data-sources/mindbody.md)      | Bookings, memberships, classes, sales, clients          |
| [Xero](/your-data-sources/xero.md)              | Accounting — contacts, transactions, the general ledger |
| [Meta](/your-data-sources/meta.md)              | Facebook & Instagram marketing and ad spend             |
| [Google Analytics 4](/your-data-sources/ga4.md) | Website traffic and where bookings come from            |
| [CSV & ClassPass](/your-data-sources/csv.md)    | Anything you can export as a spreadsheet                |

You don't need all of them. One source gives you real answers. Add the rest whenever you like.

## The rhythm every connector shares

Connecting a source follows the same four beats:

1. **Test.** You enter your key (or sign in) and we do a cheap check that it works. If it fails here, it's the key, not a broken setup — the message tells you what to fix.
2. **Connect.** We save the connection. Nothing is read yet beyond the test.
3. **Import (backfill).** We pull in your history — we suggest the last 12 months to start. This runs in the background and can take 20–30 minutes for a large studio.
4. **Process.** For most booking and accounting sources, a second step turns the raw history into the tidy, connected data the AI reads (members, sales, attendances). You'll see a **Process** button when it's ready; clicking it is safe to repeat.

> **Why two steps (import, then process)?** We land your data exactly as the provider gave it to us first, untouched, then transform a clean copy. Re-running is always safe, and if a provider changes something we can re-process without re-importing. We keep that raw copy for 30 days (long enough to re-process), then purge it — the tidy data the AI reads stays.

## What happens after that

Your connectors keep themselves current on a schedule — you don't have to re-import. They also **only fill gaps**: re-running an import never overwrites richer data you already have with something thinner.

Once a week, glance at the **Connectors** page on your dashboard to make sure everything's flowing. If something needs attention, the [Keeping your connectors healthy](/your-data-sources/operating.md) page walks you through it.

## A note on what we read

Kula Intelligence **reads** from your tools. It never writes back to them, never charges a card, never sends an email or message on your behalf. Each connector page lists exactly what that source lets us read — and what it doesn't.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kula.digital/your-data-sources/connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.