Automation Is Missing Form Data: How to Troubleshoot Field Capture and Mapping

The data flow you are debugging

Form data travels through several stages. The visitor fills the field, the form platform stores the value, the integration sends the payload, the automation maps the field and the destination record receives the value. Missing data means the value existed at one stage and was absent at the next. Your job is to find the exact stage where it dropped.

What to check first

Was the field captured in the first place

Before blaming the integration, confirm the form actually captured the value. Open the submission entry in the form platform and look at the field. If it is blank there, the problem is the form, not the automation. The field may not have been required, the visitor may have skipped it or the field may not be included in the submission payload. A value that never left the form cannot be recovered downstream.

Field names and the payload

Integrations send data using field names or keys. If the source field name does not match what the mapping expects, the value is sent but never reaches the destination. This happens when a form field is renamed, a custom field is recreated or the integration uses internal IDs instead of labels. Inspect the actual payload the integration sends, then compare those keys with the mapping. A mismatch between the payload key and the mapped field is one of the most common causes of missing data.

Mapping to the wrong destination field

Even when the payload is correct, the mapping can send the value to the wrong place. A source field mapped to an unrelated CRM field means the data lands somewhere unexpected. Custom fields with similar names are a frequent source of this. Open the mapping and confirm each source field points to the intended destination field. Field mapping problems are covered in detail in the guide on webhook data mapping wrong.

Hidden fields and conditional fields

Some forms use hidden fields for source tracking, UTMs or referral data. These fields are populated by the form platform, not the visitor. If a hidden field is empty, the script or logic that fills it may not have run, or the field may not be configured to capture the value. Conditional fields that only appear based on earlier answers can also be absent from the payload if the condition was not met. Confirm whether the field was expected to be present for that submission type.

Data types and empty values

A value can be rejected by the destination field if the data type does not match. A number sent to a text field or a date sent to a text field may be stored differently than expected. An empty string is not the same as a null value, and some CRM fields reject one but accept the other. If the value exists in the payload but not in the CRM, check the destination field type and whether it silently rejected the value.

How to test it

1. 1.Submit the form with every field filled, including hidden fields.
2. 2.Open the submission entry and confirm all values are present.
3. 3.Inspect the integration payload for the exact field names and values.
4. 4.Open the CRM record and compare each field with the submitted value.
5. 5.For any missing field, trace it through the mapping to find where it dropped.
6. 6.Fix the mapping or field name and resubmit to confirm the value now arrives.