

Syncly dashboard with connection health, queue status, and quick actions.
Connect WordPress to GoHighLevel so user registrations, profile changes, and form submissions reach your CRM without manual exports. Syncly handles GoHighLevel contact sync in both directions, maps your fields, and uses contact tags to control access to WordPress content.
Built specifically for GoHighLevel, also known as HighLevel or LeadConnector, Syncly connects through OAuth. Choose the data you want to sync, configure your mappings, and check the results in Sync Logs. Background processing handles queued work, retries temporary failures, and manages API rate limits.
The free plugin includes:
WPForms Lite and Pro
Map form answers to standard or custom contact fields, add tags, and choose whether to update or skip contacts with a matching email address. Submissions use the background queue by default; sites that enable direct sync send them during the originating request. Results are available in Sync Logs when sync logging is enabled.
Gravity Forms
Configure each form from its GHL CRM settings tab. Map contact fields, apply tags, choose how to handle existing contacts, and use the form title as the contact source. You can also delay delivery, skip spam entries, and add submission details as a contact timeline note.
Recent submission history shows sync status. Manual resend controls let you send a completed or failed submission again.
Contact Form 7
Connect Contact Form 7 submissions to GoHighLevel as part of the free plugin’s form integrations.
Syncly Pro is a separate add-on for ecommerce, course activity, and additional automation:
WPForms source labels, delays, timeline notes, and workflow enrollment require Pro. Gravity Forms source naming, delays, timeline notes, submission history, and manual resend controls are included in the free plugin.
Use the free plugin to add new WordPress users to your CRM, send form enquiries to GoHighLevel with mapped fields and tags, or manage member access through contact tags.
For stores and course sites, Syncly Pro adds purchase and learning activity to the same contact records. Those events can support follow-up workflows in GoHighLevel, such as responding to an order or a completed course.
Syncly for GoHighLevel is an independent plugin. It is not affiliated with, endorsed by, or sponsored by GoHighLevel or HighLevel.
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, mapped form answers, 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, enabled WPForms or Gravity Forms submissions are processed, 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
Syncly OAuth proxy: The plugin uses a Syncly 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 during connection, token refresh, and reconnect requests. Token refresh may run automatically in the background.
Syncly service links: https://synclyforgohighlevel.com/terms-of-service/ and https://synclyforgohighlevel.com/privacy-policy/
File logging is disabled by default. To enable temporary support logging, add define( 'SYNCLY_BRIDGE_LOG', true ); to wp-config.php. Logs may contain operational metadata and must not be exposed publicly. Apache and IIS installations are protected automatically; nginx administrators must deny web access to wp-content/uploads/syncly-logs/ before enabling logging.