> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/abc-gymsales.md).

# ABC Gymsales

## Overview

Perkville integrates with GymSales to automatically create referral leads when referred friends claim a [referral offer](https://docs.perkville.com/features/referrals.md).

When a referred friend claims an offer and the referral voucher workflow runs, Perkville sends the friend’s information into GymSales as a new Person record. This is lead delivery; it does not wait for the referring member to earn a conversion reward.

### How the integration works

The integration is triggered when a referral voucher is created in Perkville.

Perkville then:

1. Identifies the referred member and the referring member
2. Matches the Perkville location to the appropriate GymSales company/location
3. Creates a new Person record in GymSales for the referred friend
4. Passes referral details into GymSales for follow-up by the sales team

### Data sent to GymSales

The following information is sent to GymSales for the referred friend:

* First name
* Last name
* Mobile phone number
* Email address
* Birthday

Perkville also sends referral attribution details, including:

* Referrer name
* Referrer email
* Referrer phone number
* Referral source (`Perkville`)
* Contact method (`Referral`)
* Tag (`Perkville`)

### Location mapping

Each Perkville location must be mapped to a corresponding GymSales company/location ID.

This mapping ensures referral leads are created in the correct GymSales location.

### Typical use case

A gym runs a “Refer a friend” campaign in Perkville.

1. A member submits a referral
2. Perkville tracks the referral activity
3. A referral voucher is generated
4. Perkville automatically creates a Person record in GymSales for the referred friend
5. The sales team can follow up directly from GymSales

### Notes

* The integration only runs for referral-related promotions.
* Referral leads are created automatically once the referral voucher workflow is triggered.
* Existing GymSales workflows and automation can be used to manage follow-up after the Person record is created.

## Integration at a glance <a href="#capabilities-and-use-cases" id="capabilities-and-use-cases"></a>

* **Referred friend and referrer details** — Create a prospect for sales follow-up with referral attribution. **Direction:** Perkville → GymSales.
* **Location mapping** — Send each prospect to the intended sales team. **Direction:** Perkville location → GymSales company/location.

## Setup

Follow [Connecting GymSales](https://docs.perkville.com/integrations/integration-reference/abc-gymsales/connecting-gymsales.md) and confirm location mapping with your CSR.

## FAQ

### Does creating a lead complete the referral?

No. Sending a prospect to GymSales supports follow-up. The action that qualifies a referral for a reward is configured separately in Perkville.

### What happens if the prospect already exists?

Confirm matching, duplicate handling and any contact-update requirements with your CSR for the configured workflow. Do not assume that lead creation will update an existing GymSales record.

See the [GymSales partner profile](https://partners.perkville.com/partners/gymsales).

{% hint style="info" %}
**Continue reading**

Start with [Connecting GymSales](https://docs.perkville.com/integrations/integration-reference/abc-gymsales/connecting-gymsales.md) to explore the detailed guides in this section.
{% endhint %}


---

# 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://docs.perkville.com/integrations/integration-reference/abc-gymsales.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.
