Why Is My Go High Level Webhook Receiving Empty or Mismatched Fields?
If your Go High Level (GHL) webhook is receiving data from Visual Visitor but certain fields are blank or missing, the most common cause is that your workflow field mappings do not match the webhook payload being sent by your Visual Visitor account.
Understanding Visual Visitor Payload Types
Visual Visitor supports different identification products, and the data available in the webhook payload will vary depending on your account type.
Company-Level Identification
Company-level identification provides business information such as:
- Company name
- Domain
- City
- State
- Industry (when available)
Individual visitor information such as name, email address, or job title is not included.
Person-Level Identification (+Employee / +Person)
Person-level identification may include:
- First name
- Last name
- Email address
- Job title
- Company name
- Visited page URL
- Additional identification attributes based on your account configuration
How to Diagnose the Issue
- In Go High Level, open the workflow that receives the Visual Visitor webhook.
- Review the workflow's execution history.
- Expand the webhook payload and inspect the data being received.
- Compare the available fields in the payload to the fields mapped within your workflow.
If the data is present in the webhook payload but not appearing in GHL, the issue is typically a field mapping mismatch.
Resolution
- Verify which Visual Visitor identification product is active on your account.
- Update your Go High Level field mappings to match the fields contained in the webhook payload.
- Use the Test Webhook feature in Visual Visitor (Configuration > Webhook) to send a sample payload to your endpoint.
- Confirm that all desired fields are being received and mapped correctly within your GHL workflow.
Using Zapier with Go High Level
If you use Zapier between Visual Visitor and Go High Level, review your Zap configuration as well.
When webhook payload fields change or new fields become available, Zapier may continue using older field mappings until the trigger is refreshed. Re-test the webhook and update any affected field mappings before republishing your Zap.
Related Articles
How to Set Up a Webhook Integration Between Visual Visitor and Go High Level
You can push your visitor and lead data directly into Go High Level (GHL) using a webhook. This allows new identified visitors to automatically become contacts in your GHL CRM or sub-account pipeline. Step 1 - Get your GHL webhook URL 1. In Go High ...What Webhook Fields Are Available in the Visual Visitor Payload?
When Visual Visitor identifies a visitor and sends a webhook notification to your configured endpoint, the payload contains a JSON object with the visitor's identification data. Below is an overview of the key fields available in the current ...Go High Level Connector
We have added Go High Level to our growing list of connectors! With more on the road map soon, we now have the Go High Level connector. What is a connector? Visual Visitor offers a great feature called Connectors. Connectors automatically connect ...Troubleshooting Zapier Integration Errors with Visual Visitor
Common Zapier Integration Issues Zapier is a common middleware used to connect Visual Visitor with CRMs, email platforms, and other third-party applications. Below are the most frequently reported issues and their recommended solutions. Timeout ...Create a Webhook to Zapier
When setting up your Webhook integration, you have the option to send via Zapier if your system does not take a direct Webhook. In the example below, we will walk through how to send information to a Google Sheet in real-time with our Webhook ...