Antaris Lead Creation

This feature creates Antaris clients from HighLevel contacts when no Antaris client ID exists yet

The Antaris Lead Creation feature keeps HighLevel and Antaris in sync by creating a new Antaris client from a HighLevel contact, then writing the returned Antaris client ID back to the HighLevel contact.

How it works

The workflow begins when a HighLevel Contact is processed.

First, the workflow checks whether the contact already has a value in the HighLevel custom field:

"contact.antaris_client_id"

If that field already contains a value, the workflow stops. This protects against creating duplicate clients in Antaris.

If the field is empty, the workflow continues and creates a client in Antaris using the contact’s HighLevel data.

Data sent to Antaris

The workflow maps the following HighLevel contact fields into the Antaris client creation action:

• first_name

• last_name

• email

• contact_email

• cell_phone

• street

• city

• zipcode

• date_of_birth

• location_id

This allows each account or implementation to choose which HighLevel custom field identifies the Antaris location the lead should be mapped to.

Writing the Antaris client ID back to HighLevel

After the Antaris client is created, the workflow checks whether Antaris returned a client_id.

If a client ID is returned, the workflow updates the original HighLevel contact and stores that value in:

"contact.antaris_client_id"

This makes future runs idempotent: once the ID exists, the workflow will not create the client again.