> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/guides/app-reference/highlevel/integration-guides/antaris/client-and-membership-sync.md). # Client and Membership Sync ## Client Contact Sync A single **Client** workflow runs from an Antaris Client record and creates or updates the matching HighLevel contact. It syncs both basic contact information (name, email, phone, address) and membership-specific values (status, expiry date, cancellation date, freeze dates) in one pass. ### Identity resolution The action requires either an email or phone number. HighLevel treats email and phone as unique identifiers, so passing an existing contact's email or phone updates that contact instead of creating a duplicate. {% hint style="warning" %} **Duplicate risk** If a client has multiple emails or inconsistent phone formats, duplicates can be created. {% endhint %} #### Multiple memberships If a client has more than one membership, the workflow decides which membership's data (status, expiry, freeze dates, etc.) to write to the contact. It picks a "primary membership" using this priority: 1. The membership the client uses to check into the facility 2. Otherwise, the membership that was most recently updated ## Check-In Sync Middle keeps a contact's most recent gym or studio visit in sync, so HighLevel automations can react to recency of visits. Rather than simply writing the date of the triggering check-in, the workflow looks up the client's full check-in history and writes the most recent sign-in date it finds. This means a late-arriving or out-of-order check-in event can never move the field backwards. ## Online Signup Sync Middle flags contacts who joined through an online/web signup, so HighLevel can route or tag them differently from walk-in or front-desk signups. The worikflow runs from an Antaris Online Signup record and creates or updates the matching HighLevel contact. ## Data mapping

HighLevel Field	Custom?	Antaris Field	Dropdown options	Type	Antaris Source
Email	false	`email`		Email	Client
Phone	false	`home_phone` (falls back on `cell_phone` if `home_phone` does not exist)		Phone	Client
First name	false	`first_name`		Text	Client
Last Name	false	`last_name`		Text	Client
Address	false	`street`		Text	Client
City	false	`city_id`		Text	Client
State	false	`state_id`		Text	Client
Postal code	false	`zipcode`		Text	Client
`contact.antaris_client_id`	true	`client_id`		Text	Client
`contact.date_joined`	true	`date_joined`		Date	Client
`contact.membership_status`	true	`status`	Active Expired Frozen NSF Pending	Dropdown	Membership
`contact.membership_expiry_date`	true	`current_expiry_date`		Date	Membership
`contact.membership_cancelled_date`	true	`cancelled_date`		Date	Membership
`contact.membership_freeze_start`	true	`freeze_start`		Date	Membership
`contact.membership_freeze_end`	true	`freeze_end`		Date	Membership
`contact.membership_start_date`	true	`start_date`		Date	Membership
`contact.membership_type`	true	`name`		Text	Membership Type
`contact.home_location`	true	`loc_id`		Text	Membership
`contact.gender`	true	`gender`	M F O	Dropdown	Client
`contact.last_check_in_date`	true	most recent `date` accross the client's sign-ins		Date	Sign-In
`contact.web_signup`	true	`true` if the signup's `type` is online, otherwise `false`		Checkbox	Online Signup

{% hint style="info" %} **Custom fields:** for the integration to work, you'll need to create [custom fields](https://help.gohighlevel.com/support/solutions/articles/48001161579-how-to-use-custom-fields) on the HighLevel contact object. The unique key will need to match the value in the in HighLevel field column in the table above. {% endhint %} {% embed url="" %} ## Tags The Membership workflow also adds a HighLevel tag based on the Antaris membership status: | Antaris membership status | HighLevel tag | | ------------------------- | ---------------- | | Active | `active member` | | Expired | `expired member` | --- # 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, and the optional `goal` query parameter: ``` GET https://docs.middle.app/middle-docs/guides/app-reference/highlevel/integration-guides/antaris/client-and-membership-sync.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.