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

# Zapier

## Zapier Integration

BTWB Gym integrates with Zapier to automate workflows between your gym and thousands of other applications. Use triggers like new client signups, class check-ins, and subscription changes to connect with your email marketing, CRM, spreadsheets, and more.

### Quick Start

#### 1. Generate an API Key

1. Log in to [BTWB Gym Admin](https://admin.btwb.com)
2. Go to **Gym → Tools** and select **Zapier**
3. Open the **API Keys** tab and click **Create API key**
4. Copy the key that appears

#### 2. Connect to Zapier

1. Log in to [Zapier](https://zapier.com)
2. Search for **BTWB** in the app directory
3. Click **Connect**
4. Paste your API key when prompted
5. Create your first Zap using BTWB triggers

### Documentation

For detailed information, see:

* [Connecting - Managing API keys](https://btwb.gitbook.io/btwb/developers/connecting)
* [API Reference - Endpoints and authentication](/btwb/developers/api-reference.md)
* [Zapier Triggers - Available events and data](/btwb/developers/zapier-triggers.md)


---

# 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/zapier.md?ask=<question>&goal=<user_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.