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

# Integration Reference

Integration capabilities, use cases, setup guides and FAQs.

Find capabilities, use cases, setup instructions and FAQs for Perkville connections to membership systems, POS systems, CRMs, marketing tools, mobile apps and reward providers. Expand an integration in the navigation to see its feature and setup guides, including nested app guides.

## Choose the workflow

| Goal                                       | What to check in the integration guide                                                                       |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| Award points from business activity        | Supported attendance, purchase, membership and other events; eligibility filters and processing timing.      |
| Follow up with referrals                   | Whether leads are delivered, which system receives them, and how qualifying referral rewards are configured. |
| Fulfill a reward                           | Whether staff use a voucher or the connection applies a credit, service, coupon or external reward.          |
| Offer loyalty inside an app                | Whether the experience is native, an embedded tab or a link, and which member screens are supported.         |
| Use loyalty data in messaging or reporting | Supported data, direction, destinations and any custom setup.                                                |

Availability depends on the partner product/edition and your configured workflows. A partner's own features are not automatically part of its Perkville integration. Contact [Perkville Support](/overview/support.md) or your CSR to confirm requirements before launch.

## Integration directory

### A–C

* [ABC Glofox](/integrations/integration-reference/abc-glofox.md)
* [ABC Gymsales](/integrations/integration-reference/abc-gymsales.md)
* [ABC Ignite](/integrations/integration-reference/abc-ignite.md)
* [Acuity Scheduling](/integrations/integration-reference/acuity-scheduling.md)
* [Antaris](/integrations/integration-reference/antaris.md)
* [Arketa](/integrations/integration-reference/arketa.md)
* [ASF Payment Solutions](/integrations/integration-reference/asf-payment-solutions.md)
* [Booker](/integrations/integration-reference/booker.md)
* [Boulevard](/integrations/integration-reference/boulevard.md)
* [BrightLime](/integrations/integration-reference/brightlime.md)
* [Calendly](/integrations/integration-reference/calendly.md)
* [Clover](/integrations/integration-reference/clover.md)
* [Club Automation](/integrations/integration-reference/club-automation.md)
* [Club OS](/integrations/integration-reference/club-os.md)
* [ClubCom](/integrations/integration-reference/clubcom.md)
* [ClubReady](/integrations/integration-reference/clubready.md)
* [CSI Spectrum](/integrations/integration-reference/csi-spectrum.md)

### D–M

* [Daxko Engage Pro](/integrations/integration-reference/daxko-engage-pro.md)
* [Daxko Operations](/integrations/integration-reference/daxko-operations.md)
* [Emma](/integrations/integration-reference/emma.md)
* [Epifany](/integrations/integration-reference/epifany.md)
* [Erply](/integrations/integration-reference/erply.md)
* [EZ Facility](/integrations/integration-reference/ez-facility.md)
* [fitDEGREE](/integrations/integration-reference/fitdegree.md)
* [Fitmetrix](/integrations/integration-reference/fitmetrix.md)
* [Fitness BI](/integrations/integration-reference/fitness-bi.md)
* [FLiiP](/integrations/integration-reference/fliip.md)
* [Gleantap](/integrations/integration-reference/gleantap.md)
* [Gravity Forms](/integrations/integration-reference/gravity-forms.md)
* [Gym Farm](/integrations/integration-reference/gym-farm.md)
* [Hapana](/integrations/integration-reference/hapana.md)
* [HighLevel](/integrations/integration-reference/highlevel.md)
* [HubSpot](/integrations/integration-reference/hubspot.md)
* [JobNimbus](/integrations/integration-reference/jobnimbus.md)
* [Jonas Compete](/integrations/integration-reference/jonas-compete.md)
* [Jonas i4](/integrations/integration-reference/jonas-i4.md)
* [Keap](/integrations/integration-reference/keap.md)
* [Klaviyo](/integrations/integration-reference/klaviyo.md)
* [Legend](/integrations/integration-reference/legend.md)
* [Lightspeed R-Series](/integrations/integration-reference/lightspeed-r-series.md)
* [Lightspeed X-Series](/integrations/integration-reference/lightspeed-x-series.md)
* [Mailchimp](/integrations/integration-reference/mailchimp.md)
* [Mariana Tek](/integrations/integration-reference/mariana-tek.md)
* [MiGym](/integrations/integration-reference/migym.md)
* [MINDBODY](/integrations/integration-reference/mindbody.md)
* [Motionsoft](/integrations/integration-reference/motionsoft.md)
* [Motionvibe](/integrations/integration-reference/motionvibe.md)
* [MyZone](/integrations/integration-reference/myzone.md)

### N–Z

* [Paramount Acceptance](/integrations/integration-reference/paramount-acceptance.md)
* [Peak Payment](/integrations/integration-reference/peak-payment.md)
* [Pike 13](/integrations/integration-reference/pike-13.md)
* [PowerUp Business](/integrations/integration-reference/powerup-business.md)
* [PromotionVault](/integrations/integration-reference/promotionvault.md)
* [ReClique Core](/integrations/integration-reference/reclique-core.md)
* [Rock Gym Pro](/integrations/integration-reference/rock-gym-pro.md)
* [Salesforce](/integrations/integration-reference/salesforce.md)
* [SendGrid](/integrations/integration-reference/sendgrid.md)
* [Shopify](/integrations/integration-reference/shopify.md)
* [Smart Health Clubs](/integrations/integration-reference/smart-health-clubs.md)
* [Solution One Partners](/integrations/integration-reference/solution-one-partners.md)
* [Square](/integrations/integration-reference/square.md)
* [Stripe](/integrations/integration-reference/stripe.md)
* [Technogym](/integrations/integration-reference/technogym.md)
* [Traction Rec](/integrations/integration-reference/traction-rec.md)
* [Twilio](/integrations/integration-reference/twilio.md)
* [Twin Oaks](/integrations/integration-reference/twin-oaks.md)
* [Uscreen](/integrations/integration-reference/uscreen.md)
* [Virtuagym](/integrations/integration-reference/virtuagym.md)
* [VisualTouch](/integrations/integration-reference/visualtouch.md)
* [WooCommerce](/integrations/integration-reference/woocommerce.md)
* [Xplor Studio](/integrations/integration-reference/xplor-studio.md)
* [Yiftee](/integrations/integration-reference/yiftee.md)
* [Zen Planner](/integrations/integration-reference/zen-planner.md)
* [Zenoti](/integrations/integration-reference/zenoti.md)

## Changing your POS or membership system

If you are moving from one integrated system to another, contact your Perkville Customer Success Representative **before** disconnecting the current integration. The exact migration steps depend on both providers and your configured earning rules.

1. **Plan the cutover.** Confirm the old and new providers, participating locations, planned switch date, and who owns each integration.
2. **Arrange access.** Complete any required data-access authorizations for the new provider and confirm when the new connection is ready.
3. **Match customers and locations.** Review customer identifiers, membership records, email addresses, and external location IDs so activity is associated with existing Perkville accounts where possible.
4. **Avoid duplicate or missing awards.** Agree on when the old integration stops sending transactions and when the new one begins. Ask your CSR to review overlapping activities and transaction identifiers before switching.
5. **Protect existing history and balances.** Confirm how existing Perkville point balances, customer profiles, rewards, and referral records will remain accessible. Do not create replacement accounts or re-award historical activity without a reviewed plan.
6. **Test and verify.** Check a few representative members, locations, earning transactions, and applicable rewards before announcing completion of the cutover.

When your new system's membership records begin syncing, ask your CSR to review stale external member records from the old system: otherwise a previous active membership record may continue to affect eligibility. See [Transitioning membership systems](/features/customers/memberships/transitioning-membership-systems.md) for details.

For provider-specific onboarding, select the relevant integration guide in this section. For ABC Ignite, see [ABC Ignite](/integrations/integration-reference/abc-ignite.md). Contact [Perkville Support](/overview/support.md) if a member is missing, points are duplicated, or data appears to have stopped synchronizing.

{% hint style="info" %}
This is a coordination checklist, not an automatic self-service migration. Provider authorization, field mappings, and available data can differ by integration.
{% endhint %}

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

Start with [ABC Glofox](/integrations/integration-reference/abc-glofox.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.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.