Skip to main content
Use this guide when the HighLevel integration connects but imports, logs, or stage syncs do not behave the way you expect.

​
OAuth starts but does not finish

Common causes:
  • the location admin denied the OAuth request
  • the callback returned without both the code and state values
  • the saved state expired before the callback finished
What to do:
  1. retry the connection from the integration settings
  2. complete the HighLevel chooser flow in one pass
  3. reconnect if the previous state has already expired

​
The integration shows disconnected after connect

Check these first:
  • you authorized the correct HighLevel location
  • the callback completed successfully
  • the connection was not disconnected from the workspace afterward

​
Import succeeds but records are skipped

Skipped records are often expected. The importer skips records when:
  • they do not match the selected tag filter
  • they already have a sync mapping and your run is set to skip existing records
  • they matched an existing person by normalized phone or email instead of creating a new record

​
Incremental sync is not picking up a change

The incremental sync compares the contact update timestamp against the last sync time. If the record changed before the last recorded sync, it will be skipped. Try a fresh full import for a smaller tagged batch if you need to rebuild confidence in the mapping.

​
Call outcomes are not showing up in HighLevel

Push updates require an existing sync mapping. Check:
  1. the CRM contact already maps to a HighLevel contact
  2. the contact exists in the connected HighLevel location
  3. the update was one of the supported push types

​
Pipeline sync is skipping opportunities

The most common reason is an unmapped HighLevel stage. If the stage is not mapped, the opportunity is skipped by design.

​
Pipeline sync shows conflicts

Run through these checks:
  • verify the current HighLevel stage mapping is still correct
  • confirm the opportunity was not moved manually in the CRM after the last sync
  • rerun the sync after saving any updated mappings

​
Webhook events are not being accepted

If your environment validates webhook signatures, make sure the configured webhook secret matches the secret used by HighLevel. A bad signature returns an invalid-signature response instead of processing the event.

​
Next steps