✦ ✧ ✦ ·
All docs
WPForms Integration

Getting Started

What Is Syncly for GoHighLevel? System Requirements Installation Guide Quick Start: Setup Wizard Plugin Dashboard Overview Free vs Pro: Feature Comparison White-Label Domain Setup WordPress Multisite Setup

Connection & Authentication

Connecting via OAuth2 API Scope Detection Multi-Location and Agency Setup Disconnecting and Reconnecting Security Best Practices Connection Troubleshooting

Field Mapping

How Field Mapping Works Setting Up Field Mapping Sync Direction: To GHL, From GHL, Both Ways Computed and Virtual Fields Extended Field Mapping (Pro) AI-Assisted Field Suggestions (Pro)

User Sync & Tag Management

Tag Impact: Preview What a Tag Will Do Before You Apply It Tag Rules: See Every Tag Automation in One Place How User Sync Works Configuring User Sync Settings Bulk User Sync Login Tracking Ping-Pong Prevention Role-Based Tagging System Global Tags (Pro) Sync Preview and Dry Run (Pro) User Profile GHL Section

Content Restrictions

How Tag-Based Restrictions Work Page and Post Metabox Setup [syncly_restrict] Shortcode Gutenberg Restricted Content Block Elementor Widget Conditions (Pro) Archive and REST API Protection (Pro) Admin Bypass and Override Rules (Pro)

Forms & Shortcodes

Gravity Forms — Conditional Sync & Automation Embedding Syncly Forms: Overview [syncly_form] Shortcode [syncly_user_meta] Shortcode Syncly Form Gutenberg Block Syncly Form Elementor Widget Per-Form Submission Limits (Pro) Form Autofill and Logged-In-Only Mode Contact Form 7 Integration

Webhooks & Bulk Import

Setting Up Inbound Webhooks Webhook Event Types Bulk Import from GoHighLevel Webhook Troubleshooting Ping-Pong Prevention and Guards

Gohighlevel WooCommerce Integration

WooCommerce Auto-Book Calendar Appointments (Pro) WooCommerce Purchase Workflow Enrollment (Pro) WooCommerce Memberships: Grant Plans Automatically from a GHL Tag (Pro) WooCommerce Subscriptions: Grant Access Automatically from a GHL Tag (Pro) WooCommerce Integration Overview Per-Product GHL Tags (Pro) Abandoned Cart Tracking (Pro) Lead-to-Customer Conversion (Pro) WooCommerce Extended Field Mapping (Pro)

LearnDash Integration

LearnDash Integration Overview (Pro) Course Enrollment and Completion Tags (Pro) Tag-Based Auto-Enrollment (Pro) Quiz Score-Based Threshold Tagging (Pro) Lesson and Topic Completion Tags (Pro) Syncing Course Progress to GHL (Pro) LearnDash Group Sync (Pro) LearnDash Extended Field Mapping (Pro)

BuddyBoss Integration

BuddyBoss Group Sync to GHL Custom Objects BuddyBoss Group Admin Metabox Bulk Group Sync BuddyBoss XProfile Field Mapping (Pro) Family BuddyBoss Groups (Pro)

Pro Features

Gravity Forms — Conditional Sync & Automation Custom Objects: Overview (Pro) Mapping Post Types to GHL Custom Objects (Pro) Custom Object Contact Associations (Pro) Family Relationships: Overview (Pro) Managing Family Members and Invitations (Pro) Family Tag Inheritance (Pro) Conditional Navigation Menus (Pro) [syncly_family_manager] Shortcode (Pro) Analytics Dashboard (Pro) Public REST API Endpoints (Pro)

Sync Engine & Troubleshooting

Direct Sync Mode: Bypass the Queue for Tag Events How the Sync Queue Works Sync Logs and Reading Them Enhanced Sync Logs (Pro) Rate Limits and API Quotas Auto-Login Links Email Notifications Setup Advanced Settings (Cache, Batch Size, Retention) Common Issues and Solutions Frequently Asked Questions Uninstalling the Plugin

WPForms Integration

Troubleshooting WPForms Sync WPForms Workflow Enrollment (Pro) WPForms Contact Source and Send Delay (Pro) WPForms Contact Timeline Notes (Pro) WPForms Conditional Sync Rules (Pro) WPForms Contact Tags and Duplicate Handling WPForms Field Mapping WPForms Integration Overview

WPForms Integration

WPForms Integration Overview

4 min read Updated Oct 21, 2026

WPForms + GoHighLevel

Syncly connects your WPForms submissions to GoHighLevel (GHL). When someone submits an enabled form, Syncly uses the fields you mapped to create a GHL contact or update an existing one. You can also apply contact tags. Each form has its own Syncly settings, so your contact forms, lead forms, and registration forms can use different mappings and tags.

The core WPForms integration supports WPForms Lite and the paid WPForms plugin. Syncly Pro adds conditional sync rules, contact timeline notes, custom contact sources, delivery delays, and GHL workflow enrollment.

What You Can Automate

  • Contact creation and updates (Free): Send form answers to the corresponding GHL contact fields.
  • Custom field mapping (Free): Map WPForms answers to available GHL contact fields, including custom fields.
  • Contact tags (Free): Apply selected GHL tags after a contact submission is queued.
  • Duplicate handling (Free): Choose whether submissions with an existing email should update that contact.
  • Conditional sync (Pro): Send submissions only when all configured answer-based rules match.
  • Contact timeline notes (Pro): Copy the answer from a selected form field into a GHL contact note.
  • Source labels and send delays (Pro): Customize the contact source and delay delivery for up to 24 hours.
  • Workflow enrollment (Pro): Enroll a contact in a selected GHL workflow after contact synchronization succeeds, including with WPForms Lite.

Requirements

  • WordPress with WPForms or WPForms Lite installed and active.
  • Syncly installed and connected to the correct GoHighLevel location.
  • A WPForms form with an email field. Syncly must map a field to the GHL Email contact field.
  • Syncly Pro is required only for the Pro automation features listed above.

Connect a WPForms Form to GoHighLevel

1. Open the WPForms builder

In WordPress, go to WPForms → All Forms and edit the form you want to sync. If you are starting from scratch, create the form and add its fields first.

2. Open the Syncly panel

Inside the WPForms builder, open Settings → Syncly. These settings apply to this form only.

3. Enable contact synchronization

Check Send form submissions to GoHighLevel. The field mapping, contact tags, and update behavior settings appear below the checkbox.

4. Map your form fields

Under Field Mapping, choose the GHL destination for each WPForms field you want to send. At minimum, map your email field to Email. For example, map a separate first-name field to First Name, a last-name field to Last Name, and a phone field to Phone.

Important: Submissions with no usable mapped email are skipped by Syncly. The form itself may still submit successfully in WPForms.

5. Choose tags and duplicate behavior

Under Contact Tags, select any GHL tags that should be applied to contacts from this form. Under Update Behavior, keep Update existing contacts if email already exists enabled to update matching contacts, or disable it if repeat submissions should be ignored by the contact sync.

6. Configure optional Pro automation

If Syncly Pro is active, you can also configure Submission Behavior, Contact Timeline Note, Workflow Enrollment, and Conditional Sync Rules within this panel.

7. Save the form and test

Save the form in the WPForms builder, submit a test entry with a valid email address, and check the connected GHL location for the contact. Review the mapped values and selected tags. If the contact does not appear immediately, check Syncly’s Sync Logs; contact synchronization runs through the background queue.

How the Sync Works

  1. A visitor submits the form, and WPForms completes its submission processing.
  2. Syncly checks whether integration is enabled for that form and whether its GHL connection is configured.
  3. If Pro conditional rules are active, Syncly checks the submitted answers before sending anything.
  4. Syncly maps the configured answers to GHL contact fields and requires a nonempty email.
  5. The contact operation is added to Syncly’s background queue.
  6. Selected tags and applicable Pro contact notes are queued as follow-up operations linked to the contact job. Pro workflow enrollment is triggered after successful contact sync.

The form does not need to wait for the GoHighLevel API request to finish. A successful WPForms confirmation does not necessarily mean the background CRM job has already completed.

Common Use Cases

  • Contact form: Save contact details and add an inquiry tag.
  • Lead form: Map an interest or budget field to a GHL custom contact field.
  • Consultation request: Use Pro to copy the visitor’s message into a contact note and enroll the contact in a follow-up workflow.
  • Qualified leads: Use Pro conditional rules to sync only submissions that match your chosen criteria.

Troubleshooting

If a submission does not create or update a GHL contact, first check that the GHL connection is active, the form’s Syncly checkbox is enabled, a WPForms email field is mapped to GHL Email, and the form was saved. For Pro, check conditional rules and delivery delays. Then review Syncly → Sync Logs for pending or failed jobs.

What are your Feelings