Make Automation Data Mapping Is Wrong: Why Values Go Into the Wrong Fields

The mapping flow you are debugging

Data flows from the source value through the module output, through the field mapping and into the destination field. Wrong mapping happens when the output is mapped to the wrong field or the data type does not match. The source value is correct but it lands in the wrong place. Find the stage where the value is correct on one side and wrong on the other.

What to check first

Source value versus mapped value

First confirm the source value is correct. Then inspect the module output bundle to see the value that came through. If the value is correct in the source but wrong in the destination, the mapping is the problem. If the value is wrong in the output, the problem is upstream. Isolating where the value is correct and where it becomes wrong tells you which step to fix.

Wrong destination field selected

The destination module maps each output to a destination field. If the wrong field is selected, the value lands in the wrong place. This is common with custom fields that have similar names or when a field was renamed. Open the destination module and confirm each output maps to the intended field. Check the field ID where the platform shows it, because labels can be misleading.

Bundles and multiple records

Make processes data in bundles. A scenario that handles multiple records processes one bundle at a time. If the mapping assumes a single bundle but the scenario receives multiple, values can land in the wrong place or only the first record maps correctly. Check how the scenario handles multiple bundles and confirm the mapping works for each one, not just the first.

Nested data and arrays

Source data can be nested inside objects or arrays. If the mapping points to the wrong level of the structure, the value appears wrong even though it is there. Inspect the output bundle structure and confirm the mapping points to the correct path. Nested data and arrays are a common source of mapping errors, and the same problem appears in the general webhook data mapping guide.

Data type mismatches

A destination field expects a specific data type. A text value sent to a number field or a date in the wrong format can be rejected or stored incorrectly. Check the destination field type and confirm the output matches it. Some platforms convert automatically and some reject the value, so behavior varies.

How to test it

1. 1.Confirm the source value is correct in the source application.
2. 2.Inspect the module output bundle for the value.
3. 3.Open the destination module and check each field mapping.
4. 4.Confirm the destination field data type matches the value type.
5. 5.Check bundle handling if the scenario processes multiple records.
6. 6.Run the scenario and check the destination record for the mapped value.