Skip to main content
The direct HighLevel integration is no longer available. On the Integrations page, the HighLevel card shows No longer available and the button Use webhooks instead, and HighLevel can no longer be selected when you create an event.To send GoHighLevel / HighLevel events to Cometly, follow Send HighLevel events with webhooks.

If you already have HighLevel events

Events you created with the direct integration stay in Events Manager, and their history stays in Cometly. They can no longer receive new data. To keep tracking the same event, send the data from HighLevel with a Cometly webhook instead, as described in Send HighLevel events with webhooks.

Pixel and form tracking on HighLevel

These still apply when you send events with webhooks:
  • Install the Cometly pixel in your GoHighLevel account with the GoHighLevel pixel installation guide. The pixel captures key form field data on your GoHighLevel pages (first name, last name, email and phone number), so a new event sent to Cometly can be linked to the visitor’s original journey and its source data.
  • If you use embedded GoHighLevel forms, make sure they capture form field data: see GoHighLevel form capture.

How the direct integration worked (for reference)

The rest of this page describes the retired setup flow. You cannot start it any more; it is kept so you can understand how an existing HighLevel event was configured.

Step 1: Create the event

On the Events Manager page, you clicked Create Event. In the dialog you:
  1. Selected HighLevel as the App / Integration.
  2. Chose the event name (a default event or a new custom event).
  3. Clicked Create.

Step 2: Configure the event and the HighLevel account

You clicked Configure next to the new event. Then you chose a connected HighLevel account and a trigger:
  • App: pre-selected as HighLevel.
  • Account: the HighLevel account to use, or Connect new account for a first connection. Only a HighLevel Sub-Account could be connected. Several Sub-Accounts could be connected, each as its own connection.
  • Trigger: when the event was sent to Cometly. The triggers were:
Once selected, the Account and Trigger could not be changed. Using a different account or trigger meant creating a new event. To test, you fired the trigger in HighLevel (for example by submitting a form, completing a payment, booking an appointment or moving an opportunity to a new stage), clicked Check for Data, chose the matching record and clicked Continue With Selected Record.

Step 3: Configure mapping

You mapped the HighLevel data fields to Cometly fields. Email and Event Time were required:
  • Email: the email address field from the selected record.
  • Event Time: usually the dynamic option “The time we receive the event”.
Add Field mapped additional data such as first name, last name, phone number, amount, custom tags or pipeline stage. Save & Continue moved to the next step.

Step 4: Configure filters and activate the event

Filters controlled which HighLevel events were recorded in Cometly. They were optional, and useful when tracking changes to contact status or opportunity stages. Common uses:
  • Only record the event when the opportunity stage equals “Proposal Sent”.
  • Only record the event when a custom field (such as plan type) equals “Enterprise”.
  • Skip test or unqualified contacts.
Each filter had a field (for example stage, tag or owner), a condition (for example (text) is, (text) contains or (text) starts with) and a value. The screen showed PASS or FAIL for each filter against the test record, and a message when the webhook would not have continued. Activate switched the event on. The same mapping and filtering steps are used for webhook events today. See the Cometly webhooks guide.