Syncly for GoHighLevel

Description

Syncly for GoHighLevel connects WordPress sites with GoHighLevel CRM. It helps site administrators synchronize WordPress users, WooCommerce customers and orders, BuddyBoss profile fields, LearnDash activity, tags, custom fields, embedded forms, and webhook events.

The plugin includes OAuth2 connection handling, automatic token refresh, visual field mapping, contact synchronization, role-based tagging, membership content restrictions, webhook processing, queue management with Action Scheduler, and sync logs.

This plugin is not affiliated with, endorsed by, or sponsored by GoHighLevel or HighLevel.

External services

This plugin connects to external services to provide CRM synchronization and OAuth authentication. These services are required for the plugin to connect WordPress data with a GoHighLevel account.

GoHighLevel and LeadConnector APIs: The plugin sends CRM-related data such as contact names, email addresses, phone numbers, WordPress user profile data, tag names, custom field values, WooCommerce customer/order data when enabled, BuddyBoss profile data when enabled, LearnDash activity when enabled, webhook payloads, and form identifiers. Data is sent when an administrator connects the plugin, runs sync actions, saves mapping/settings that require metadata lookup, users register or update profiles, connected ecommerce/community/LMS events occur, webhooks are received, or embedded GoHighLevel forms are displayed.

GoHighLevel service links: https://www.gohighlevel.com/terms-of-service and https://www.gohighlevel.com/privacy-policy

LabGenz OAuth proxy: The plugin uses a LabGenz proxy endpoint during OAuth token exchange, token refresh, and reconnect flows so OAuth client credentials are not distributed inside the plugin. The proxy receives OAuth authorization codes, refresh tokens, location/account identifiers, and related token request metadata only when an administrator connects or refreshes the GoHighLevel connection.

LabGenz service links: https://labgenz.com/terms-of-service/ and https://labgenz.com/privacy-policy/

Blocks

This plugin provides 2 blocks.

  • GoHighLevel Form Embed a GoHighLevel form with customizable settings.
  • Restricted Content Show or hide content based on user's GoHighLevel tags.

Installation

  1. Upload the plugin folder to /wp-content/plugins/syncly or install the plugin ZIP through Plugins > Add New > Upload Plugin.
  2. Activate Syncly for GoHighLevel from the Plugins screen.
  3. Open the Syncly admin menu.
  4. Connect your GoHighLevel account using OAuth.
  5. Configure field mappings, sync settings, forms, webhooks, and optional integrations as needed.

FAQ

Do I need a GoHighLevel account?

Yes. Syncly connects WordPress to a GoHighLevel account and requires authorization through GoHighLevel OAuth.

Is this an official GoHighLevel plugin?

No. Syncly for GoHighLevel is an independent plugin and is not affiliated with, endorsed by, or sponsored by GoHighLevel or HighLevel.

Does the plugin include Action Scheduler?

Yes. Action Scheduler is included through Composer dependencies for background queue processing.

Reviews

Read all 1 review

Contributors & Developers

“Syncly for GoHighLevel” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.4.7

  • Security hardening: removed registration-time trust of request role input and now uses persisted user role data for role-tag sync.
  • Security hardening: strengthened admin AJAX guards by enforcing capability checks alongside nonce validation.
  • Security hardening: required admin capability for OAuth admin callback handling before processing query parameters.

1.4.6

  • Removed legacy manual API-key connection pathways from runtime client flow and kept OAuth-only auth handling.
  • Added generated minified asset ignore rules for local development while preserving CI-built production minification.
  • Minor reviewer-compliance hardening and cleanup updates.

1.4.5

  • WordPress.org review hardening: moved Global Tags and AI-assisted field suggestions ownership fully to Syncly Pro, with free-plugin notice/delegation only.
  • Aligned reviewer-facing copy and changelog notes with current free/pro feature boundaries.
  • Kept Sync Preview as Pro-only in free response paths and validated packaging guard checks.

1.4.3

  • Addressed WordPress.org review feedback for public contact-link validation, unique transient prefixes, and restriction feature availability.
  • Added GitHub Actions packaging checks and release ZIP generation for production submissions.

1.4.2

  • Prepared production package for WordPress.org review.
  • Updated packaged assets and asset versioning.
  • Removed development-only files from the production build.

1.4.1

  • Removed remaining locked/mockup screens (Forms add-on preview, Sync Logs detail preview) from the free plugin; replaced with plain upgrade notices.
  • Moved Family Relationships and Login Sync settings tabs to the Pro plugin; the free plugin no longer ships any disabled preview of these features.
  • Added a single “Upgrade to Pro” settings tab listing Pro-only features; it’s automatically hidden once Pro is active and licensed.
  • Removed remaining legacy branding identifiers from the free and Pro plugins.
  • Replaced hardcoded plugin name strings with a single constant for consistent display text.
  • Removed a non-system font reference from the admin UI in favor of WordPress’s own font stack.

1.4.0

  • Renamed internal namespace, hooks, and identifiers to Syncly throughout the codebase.
  • Removed locked/disabled preview screens from the free plugin; Pro-only features are now referenced via a plain upgrade link instead of an in-app mockup.
  • Moved inline scripts/styles to wp_enqueue_script/wp_enqueue_style.
  • Bundled SweetAlert2 locally instead of loading it from a CDN.
  • Updated Chart.js to the latest stable release.

1.3.17

  • Updated plugin branding for the Syncly slug.
  • Added WordPress.org external service disclosures.
  • Updated payment and upgrade links to the HighLevelSync home page.
  • Improved review compliance for request sanitization and escaped filtered output.