GoHighLevel Custom Fields Not Updating: Common Causes and Fixes

Why a custom field stays empty or stale

A custom field updates when an action writes a value to it. If the action never runs, runs with the wrong value or writes to the wrong field, the value does not change. The fix starts with identifying which action should update the field and confirming it actually executed.

What to check first

Which action should update the field

Before anything else, confirm what is supposed to update the field. It could be a form, a workflow action, an import, an integration or a webhook. If you do not know which action owns the update, you cannot tell whether it ran. Start by listing every possible source of the update.

What value should be written

An action that updates a custom field writes a specific value. If that value is empty, wrong or mapped from a field that was itself empty, the custom field does not update the way you expect. Check what the action is set to write and where that value comes from.

Whether the action ran

Use the workflow history to confirm the update action actually executed. If the workflow stopped before the action or the contact never reached it, the field never gets updated. The history tells you whether the action ran or was skipped.

Field mapping

An update can write to the wrong field if the mapping is off. This happens often with imports, integrations and webhooks where fields are matched by name or ID. Confirm the action writes to the exact custom field you are checking, not a similarly named one.

Empty values and data types

Some updates fail silently when the source value is empty or when the data type does not match. A text value written to a number field, or an empty value overwriting a real one, can look like the field did not update. Check the source value and the field type.

Existing records and contact matching

An update from a form or integration only works if it matches the right contact. If the update creates a new contact instead of updating the existing one, the original record stays unchanged. Confirm the action updates the existing contact rather than creating a new one.

How to diagnose a custom field that does not update

1. 1.Identify the custom field and the action that should update it.
2. 2.Check the value the action is set to write.
3. 3.Confirm the action ran in the workflow history.
4. 4.Confirm the value is mapped to the correct field.
5. 5.Check the source value and the field data type.