Nested Object Editor with Preserved Key Manifest and Change Detection

How it works

1. 1.Run the manual trigger; a Code node emits fictional nested-map data with the production schema
2. 2.A Code node builds the sorted key manifest before editing into keyManifestBefore
3. 3.A Code node flattens the map via Object.entries into items with key, stringified value and sourceMap
4. 4.A Set node uppercases value with includeOtherFields:true to keep key and manifests
5. 5.A Code node recomputes the manifest into keyManifestAfter
6. 6.An If node compares manifests literally: true to Merge input 0, false via NoOp to Merge input 1
7. 7.Merge appends both paths, then a final Code node returns one consolidated report item

Use cases

• Editing values of hierarchical object maps while documenting all original keys
• Detecting deleted or renamed fields during JSON processing in n8n
• Converting nested maps into explicit inspectable items without [object,Object]
• Schema integrity auditing before handing data to downstream stages

Requirements

• n8n 2.44.4 with built-in nodes only: manualTrigger, code, set, if, merge, noOp, stickyNote
• No credentials or external connections; sample data is fictional test data
• For production, replace the sample Code node with a real source using the same nestedMap schema

Setup and testing in n8n

1. Import the JSON into n8n and run Execute Workflow; expect one report with manifestMatch=true and four records
2. Inspect records: no [object,Object], every original key is an independent key field, value uppercased
3. For mismatch, delete the customer_delta item from sample data or flatten output and rerun; If routes through NoOp into Merge and manifestMatch=false without stopping
4. For empty input set nestedMap to {}; output is one empty item with two equal empty manifests and no error

Service Value

Ready-made workflow template for automation delivery and service execution.