✦ ✧ ✦ ·
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 Field Mapping

3 min read Updated Oct 21, 2026

Overview

Field Mapping tells Syncly which WPForms answers should be sent to which GoHighLevel (GHL) contact fields. Mappings are configured separately for each form, inside the WPForms builder.

Before You Start

  • Connect Syncly to your GHL location.
  • Open an existing WPForms form that contains the fields you want to sync.
  • Make sure the form has an email input. At least one WPForms field must map to the GHL Email field.

Configure Field Mapping

  1. In WordPress, go to WPForms → All Forms and edit the form.
  2. Open Settings → Syncly.
  3. Enable Send form submissions to GoHighLevel.
  4. In Field Mapping, find each WPForms field in the left column.
  5. Use its GoHighLevel Field dropdown on the right to choose the destination.
  6. Save the form and submit a test entry.

Example Mapping

WPForms field GoHighLevel contact field Purpose
Email Address Email Required to identify the contact
First Name First Name Store a separate first name
Last Name Last Name Store a separate last name
Phone Number Phone Store the submitted phone number
Area of Interest Your GHL custom contact field Preserve additional lead information

Email Mapping Is Required

Syncly requires a mapped email value before it queues a contact sync. If you do not map an email field, or the submitted answer produces an empty email value, Syncly skips that submission. In the builder, Syncly also shows an email-mapping warning when the required mapping is missing.

GoHighLevel Custom Fields

Custom contact fields can be selected from the GoHighLevel field dropdown when they are available in the connected location. Syncly sends them as GHL custom fields using their IDs. Create the desired custom contact field in GoHighLevel first if it does not appear in the selector, then reload the builder to refresh the available fields.

Names, Checkboxes, and Multi-Select Answers

  • Name fields: When a WPForms compound Name field is mapped to GHL First Name or Last Name, Syncly uses the corresponding part when available.
  • One destination per field: Each WPForms field row has one GHL destination. If you want to send both first and last names reliably, use separate WPForms fields and map them individually.
  • Multiple answers: Checkbox, multi-select, and other array-valued answers are flattened into a comma-separated text value before sending.
  • Unmapped or empty fields: Fields with no selected GHL destination, or with an empty submitted value, are omitted from the contact payload.
  • Display-only fields: WPForms HTML, Content, Divider, Page Break, and CAPTCHA fields are excluded from the field-mapping list.

Test Your Mapping

  1. Save the form and submit a test entry with a unique email.
  2. Allow the background sync to process.
  3. Open the matching contact in GoHighLevel and compare the contact fields against your test answers.
  4. If any value is missing, return to Settings → Syncly and verify the mapping and submitted value.
  5. Check Syncly → Sync Logs if the contact was not processed.

Troubleshooting

  • No GHL fields shown: Verify the Syncly GHL connection, then reload the builder.
  • Email warning: Choose the GHL Email field for one of your WPForms inputs.
  • Custom field missing: Verify that the contact custom field exists in the connected GHL location.
  • Last name missing: Use a separate Last Name form field if you need to map both parts independently.
  • Checkbox answers look different: Multi-value answers are stored as comma-separated text in the mapped GHL field.
What are your Feelings