Taggie docs
HighLevel sync
Connect a location, understand auto-sync, read drift states, resolve conflicts and inspect sync history.
Each workspace connects to one HighLevel location through OAuth. The connection gives Taggie a remote copy to manage; it does not turn the two systems into an invisible last-write-wins merge.
Connect a workspace
Open Settings → Integrations and choose the HighLevel connection action. Connection state, auto-sync controls and recent sync information live in the same panel.
Reconnecting to the same location keeps the existing links between Taggie tags and their remote copies.
What auto-sync does
Auto-sync is on by default. It batches a burst of nearby edits into one run and sends only names that changed.
You can also sync a single group manually or run a workspace-wide sync.
Auto-sync does not decide a conflict. When the remote tag vanished or an unlinked HighLevel tag already owns a requested name, Taggie pauses and asks for a human decision.
Read the status badges
Every tag states its relationship to HighLevel in words:
- Synced — the local and linked remote records agree.
- Drifted — the linked records no longer agree.
- Error — the last operation could not complete.
- Not synced — the tag has not been sent.
- Renamed in CRM — someone changed the linked tag in HighLevel.
- Deleted in CRM — the linked remote tag is gone.
Folders roll up issues from the groups below them, so you can see drift without opening every group.
Check CRM
Use Check CRM to refresh remote renames and deletions when you need a current comparison. Contact counts are shown per tag and per group with the time they were taken; treat the timestamp as part of the count.
Retry and history
A run that fails halfway retries on its own. It backs off between attempts and stops loudly after five failures.
Open Settings → Sync history to see complete, partial and failed runs. Expand a run to inspect the individual operations rather than relying on one summary state.
Deleting safely
When you delete a mapped tag, Taggie waits 15 seconds before telling HighLevel. The Undo action remains available for 12 seconds.
That pause matters because deleting a tag in a CRM also removes its contact associations.
Disconnecting
Disconnecting makes the mappings inert and stops sync. It does not send a cleanup operation to HighLevel.
Syncing stops and the tag mappings go inert. None of your tags are changed.