Connect HighLevel
Create a HighLevel contact with a Private Integration Token and location ID.
Create a contact in the intended HighLevel sub-account from an accepted HoneyFalcon lead.
Why it matters
The preset makes the HighLevel location boundary explicit, reducing manual contact entry without hiding which account receives the data. HoneyFalcon records the HTTP handoff while HighLevel remains the place to confirm the resulting contact.
Where to work
Prepare the Private Integration Token and location ID in HighLevel. Then open Company -> Connectors, select New connector, choose HighLevel contact, and select Load preset.
Steps
- Create or select a Private Integration for the target HighLevel sub-account with contacts.write permission.
- Copy the Private Integration Token into a password manager and copy the exact location ID for the same target.
- Load the HighLevel contact preset in HoneyFalcon and confirm the services.leadconnectorhq.com/contacts/ Destination URL.
- Paste the token into Credential and keep the Authorization Bearer secret placeholder and Version 2021-07-28 headers.
- Replace REPLACE_WITH_HIGHLEVEL_LOCATION_ID in the request template with the exact location ID.
- Review Payload fields, contact mapping, and Successful HTTP status 201.
- Run Test draft with a synthetic identity, then Create connector or Save changes, Activate the saved revision, and verify a new synthetic contact in the intended HighLevel location.
See it in HoneyFalcon
Step 1 of 5: HighLevel preset selected in the connector editor.
Step 2 of 5: HighLevel destination and protected credential controls.
Step 3 of 5: HighLevel payload fields and request template.
Step 4 of 5: HighLevel request template and destination field mapping.
Step 5 of 5: HighLevel endpoint and Successful HTTP statuses to review before creation.
Keep the credential and location aligned
Prepare one target boundary
The Private Integration Token must have contacts.write permission for the intended HighLevel account or sub-account. The location ID in the request template must identify that same target.
Record the target in your internal connector inventory without exposing the token.
Preserve the current API contract
The preset posts to services.leadconnectorhq.com/contacts/ and supplies Authorization Bearer and Version 2021-07-28 headers. It does not use the retired rest.gohighlevel.com/v1 endpoint.
Keep the token in Credential so the template and visible headers contain only the supported secret placeholder.
Replace the location marker
Replace REPLACE_WITH_HIGHLEVEL_LOCATION_ID with the exact target location ID before saving. The template also maps contact and address values and includes the delivery ID in source for bounded correlation.
Review Payload fields whenever the template changes so every HoneyFalcon placeholder remains selected.
Verify the contact in the intended location
HTTP 201 is the preset's successful response. Delivered records that response but cannot prove that an operator is viewing the correct HighLevel location or that every final field is as intended.
Search the target location for the unique synthetic identity and compare its fields before enabling production data.
Use a Private Integration Token and location ID that belong to the same intended HighLevel target. Treat HTTP 201 as the delivery result, then verify the contact inside that exact location.
The HighLevel connector is ready when
- The current contacts endpoint, Bearer header, version header, and HTTP 201 contract remain intact.
- The setup marker has been replaced with the exact location ID for the token's intended target.
- Payload fields match every HoneyFalcon placeholder used by the request.
- A synthetic delivery is traceable in HoneyFalcon and the expected contact appears in the intended HighLevel location.