Reversible Nested Key Rename with Translation Manifest

How it works

1. 1.Run the Manual Trigger; a Code node emits a fictional hierarchical sample payload
2. 2.Edit the MAP constant in the rename node to match your source and target schemas
3. 3.The rename node outputs the renamed structure, preserved-key manifest, and reverse map
4. 4.The output branches: the manifest flows directly to Merge input 0, while the reverse chain verifies round-trip equality and reaches Merge input 1 via the IF
5. 5.A mismatch routes to the NoOp failure endpoint
6. 6.A final Code node aggregates both records into a single report item

Use cases

• Transforming nested JSON payloads between two schemas with a safe return path
• Documenting which keys were renamed versus preserved before touching target systems
• Automatically validating translation maps before deployment

Requirements

• n8n 2.44.6 with code, set, if, merge, noOp, stickyNote and manualTrigger nodes
• No credentials and no network calls — fully local processing

Setup and testing in n8n

1. Import the JSON into n8n and execute from the Manual Trigger
2. Verify roundTripVerified is true and preservedKeys includes phone_type, qty, customer
3. Edit MAP so two keys map to the same target to exercise the failure branch via NoOp
4. Replace the sample node with a real trigger emitting {json:{payload:...}} of the same schema

Service Value

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