> For the complete documentation index, see [llms.txt](https://btwb.gitbook.io/btwb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://btwb.gitbook.io/btwb/admin/tools-and-integrations.md). # Tools & Integrations This article is an overview of the Tools page — BTWB's directory of integrations with Zapier, Mailchimp, and AI agents such as Claude — and where to find each one's full setup guide. ### Overview **Gym → Tools** is where BTWB connects to the software you already run your business on. It opens on a directory of **Available integrations**, one card per tool: **Zapier**, **Mailchimp**, and **AI Agents (MCP)**. Click a card to open that integration's own page; **Back to Tools** returns you to the directory. ![The Tools page — Zapier API keys and the AI Agents (MCP) tab](https://283006627-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZrefv5JliAQavbeRiIvd%2Fuploads%2Fgit-blob-34fb45ed928d64a786087c54050167bdcc785ac8%2Ftools-integrations.gif?alt=media) *** ### Zapier Zapier lets you sync BTWB with thousands of other apps — spreadsheets, CRMs, Slack, and more — using the **BTWB** app in your Zapier account. The Zapier page has two tabs: * **Getting Started** — the three setup steps: create a Zapier account, create an API key, and paste it into Zapier. * **API Keys** — your organization's keys. Click **Create API key** and the new key appears at the top of the list, already revealed so you can copy it. Other keys stay masked until you click **Reveal key**. To revoke a key, click its trash icon. Revoking is **permanent** — as the confirmation warns, *"Selecting 'YES, REVOKE' will permanently deactivate this API Key."* Any Zaps using that key stop working, and you'd need to create a new key to reconnect. For the full setup, see [Zapier](/btwb/admin/tools-and-integrations/zapier.md). *** ### Mailchimp The **Mailchimp** page connects your Mailchimp account to BTWB so your client data syncs to your email marketing automatically. There are no keys to copy: 1. Click **Link Mailchimp Account** and sign in to Mailchimp in the new tab. 2. Back in BTWB, the status reads **Connected (Pending)**. If it hasn't changed, click **Reload Status**. 3. Under **Select Audience and Activate**, choose the Mailchimp audience to sync to and click **Activate Integration**. The integration isn't active until you do this. The status changes to **Connected & Activated**. **Disconnect** unlinks your Mailchimp account. To use your BTWB data in Mailchimp, see [How to Use Mailchimp with BTWB](/btwb/admin/tools-and-integrations/mailchimp.md). *** ### AI Agents (MCP) The **AI Agents (MCP)** page connects an AI assistant such as **Claude**, **ChatGPT**, **Grok**, or a **Notion** custom agent to your gym's data through the Model Context Protocol, so you can ask questions about your gym in plain language. * The **Overview** tab lists the **Available MCP servers**, each with a URL to copy: **BTWB Org → Operations** (memberships, billing, revenue, attendance, and client reports), **BTWB Org → Coaching** (your members' training, health, planning, and social data), and **BTWB Library → Training** (the shared library of workouts, movements, and programming). * The **Claude**, **ChatGPT**, **Grok**, and **Notion** tabs have each assistant's setup steps. Each one connects with a server URL and your BTWB sign-in, so there's no Client ID or secret to paste. See [How to Connect BTWB to Claude](/btwb/admin/tools-and-integrations/how-to-connect-btwb-to-claude.md), which covers all four. * The **Other agents** tab has the technical details for any other MCP client. BTWB allows Claude, ChatGPT, Grok, and Notion; to use another assistant, contact support. * **The agent signs in as you, so it only sees what you're allowed to see.** You can revoke its access at any time from that assistant's settings. * Agents mostly read your data. On the **Operations** server, an owner's or admin's agent can also change a booking, such as a check-in, a cancellation, or a credit, and can ask a client to sign a document. No agent can charge a card, edit a membership, or change your class schedule. *** ### Mindbody If you run your gym in Mindbody, the **Mindbody Sync** keeps your gym's member list in BTWB matched to Mindbody. It isn't on the Tools page: you set it up in the Coaching Console at **coach.btwb.com**, under **Integrations → MINDBODY**. See [How to Sync Mindbody with BTWB](/btwb/admin/tools-and-integrations/mindbody.md). *** ### Notes for Admins and Coaches * The Tools page is available to owners, full admins, and staff with the **Tools** permission. The **AI Agents (MCP)** card only appears for **owners and full admins**. * Treat Zapier API keys like passwords — anyone with a key can read your gym's data through the integration. Create a separate key per Zapier connection so you can revoke one without breaking the others. * Revoked API keys can never be reactivated; create a new key instead. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://btwb.gitbook.io/btwb/admin/tools-and-integrations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.