> 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/antaris-lead-creation.md).

# Antaris Lead Creation

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.


---

# 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/antaris-lead-creation.md?ask=<question>&goal=<endgoal>
```

`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.