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.

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.

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

email

Email

Client

Phone

home_phone (falls back on cell_phone if home_phone does not exist)

Phone

Client

First name

first_name

Text

Client

Last Name

last_name

Text

Client

Address

street

Text

Client

City

city_id

Text

Client

State

state_id

Text

Client

Postal code

zipcode

Text

Client

contact.antaris_client_id

client_id

Text

Client

contact.date_joined

date_joined

Date

Client

contact.membership_status

status

Active Expired Frozen NSF Pending

Dropdown

Membership

contact.membership_expiry_date

current_expiry_date

Date

Membership

contact.membership_cancelled_date

cancelled_date

Date

Membership

contact.membership_freeze_start

freeze_start

Date

Membership

contact.membership_freeze_end

freeze_end

Date

Membership

contact.membership_type

name

Text

Membership Type

contact.home_location

loc_id

Text

Membership

contact.gender

gender

M F O

Dropdown

Client

Custom fields: for the integration to work, you'll need to create 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.

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

Last updated

Was this helpful?