Recursive Nested JSON Key Rename with Preserved-Keys Manifest

How it works

1. 1.Run the manual trigger to emit the fictional nested sample
2. 2.Rename Engine applies the dictionary recursively over objects and arrays
3. 3.The engine collects a manifest of renamed, preserved and conflicting key paths
4. 4.If compares original vs new total key counts and routes true or false
5. 5.Set adds a text report keeping all other fields; a sticky note documents the dictionary

Use cases

• Normalizing hierarchical API responses before storage
• Renaming integration field names without data loss
• Auditing schema transformations with a reviewable manifest

Requirements

• No credentials; all processing is local
• For real input remove the sample node and feed same-schema data into Rename Engine
• Edit RENAME_MAP inside the Rename Engine Code node

Setup and testing in n8n

1. Import the workflow in n8n and click Execute Workflow
2. Verify the manifest and the 17/17 key count (7 renamed, 10 preserved) on the true branch
3. Replace the sample value with a string or null to see the invalid item routed to Flag Silent Loss
4. Add a pre-existing 'town' key to the sample to prove collision detection in manifest.conflicts without silent overwrite
5. Add a dictionary entry and rerun to confirm renaming at all levels

Service Value

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