When inspecting the output of a create/update block in an automation, you see a JSON representation of the object that needs to be created/updated. However, this JSON representation is bound to the way that the block is configured, and can differ from the JSON that is sent to the API. This can happen when custom code is applied right before the JSON is sent to an API, and it can modify the structure of the JSON.
Example:
1. JSON object that is seen when checking a block:
2. JSON object that is sent to the API for the same block:
As you can see, the field 'extra_values" which contains a nested object is not used, instead, the nested object is merged with the rest of the JSON. The JSON representation from the block can differ from the JSON expected by the API, so it should not be used as validation.