Dotted Key Normalizer with Collision Detection and Literal Round-Trip Verification

How it works

1. 1.Run the manual trigger; the sample node emits a valid nested item with dotted keys and arrays plus an intentional collision item (a.b with a b)
2. 2.The normalizer scans all levels, replaces dots with spaces, logs each rename with its path, records colliding paths and discards the modified copy of colliding items
3. 3.The verification node reverses only the rename log, compares JSON.stringify literally with the original and emits the match result
4. 4.A Set node adds stage fields with includeOtherFields:true, then the IF node routes matched items to success and mismatched/colliding items to failure without stopping the workflow
5. 5.Merge collects both branches into separate inputs and a final Code node emits one report with counts and per-item detail

Use cases

• Normalizing dotted JSON keys from external systems before stages requiring simple names
• Safely converting dot notation to spaces inside deep structures with arrays and nested objects
• Detecting silent field merging when two keys produce the same resulting key

Requirements

• n8n 2.44.6 with manual trigger, code, set, if, merge, noOp and stickyNote nodes
• No credentials or network calls; the dot-to-space map and location-based rename log are embedded in code
• For real data replace the sample payload node with a Webhook or HTTP Request node using the same {payload:{...}} schema

Setup and testing in n8n

1. Import the JSON in n8n and execute the Manual Trigger node
2. Expect one final report: 2 items, 1 normalized, 1 collision with paths payload.a.b and payload.a b, 1 verified match, allPassed=false
3. For a fully valid case delete the second sample item and confirm allPassed=true and verifiedMatches=1
4. Add a key containing an original space with no dotted equivalent and confirm the round trip still matches literally because reversal uses the rename log

Service Value

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