> 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 Middle's Antaris integration with HighLevel keeps contacts up to date with client and membership data synced from Antaris. ## Client Contact Sync ### Workflows There are two workflows: 1. **Client:** Runs from an Antaris Client record and creates or updates the matching HighLevel contact. 2. **Membership:** Runs from an Antaris Membership record and creates or updates the matching HighLevel contact using the membership’s related client. {% hint style="info" %} **Why two workflows?** Use the Client workflow to keep basic contact information synced. Use the Membership workflow to keep membership-specific values synced, such as status, expiry date, cancellation date, and freeze dates. Together, these workflows keep HighLevel contacts aligned with the latest Antaris client and membership data without relying on manual imports. {% endhint %} ### 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. #### Duplicate risk If a client has multiple emails or inconsistent phone formats, duplicates can be created. #### Multiple memberships Multiple memberships tied to the same client will still resolve to a single contact because identity is based on the client’s email/phone ### Data mapping #### Fields

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_type`	true	`name`		Text	Membership Type
`contact.home_location`	true	`loc_id`		Text	Membership
`contact.gender`	true	`gender`	M F O	Dropdown	Client

{% 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.