Parallel Array Semantic Namer with Conflict Guard

How it works

1. 1.Run Manual Trigger; a Code node emits a fictional object with parallel arrays including an intentional name conflict
2. 2.Infer Names & Detect Conflicts traverses the structure, infers one name per array and singularizes single-element arrays
3. 3.Identical inferred names are grouped; occurrences after the first get an @parent-path suffix and all group records are flagged with conflict_detected and conflict_detail
4. 4.If splits conflicting records (true branch) from clean records (false branch)
5. 5.Set nodes add record_status with includeOtherFields, Merge (append) recombines both branches, NoOp ends the flow

Use cases

• Stable column naming before splitting parallel report arrays into records
• Detecting parallel-array name collisions before they reach downstream reports
• Normalizing field names from nested JSON sources

Requirements

• n8n 2.44.6+ with code, if, merge, set, stickyNote and manualTrigger nodes
• No credentials or external calls — fully self-contained

Setup and testing in n8n

1. Import the workflow JSON into n8n
2. Execute Manual Trigger; expect 7 records: 3 named items and 3 named items@shipment (all conflict_resolved) plus 1 record note with status clean
3. Edge case: replace the payload with an empty or array-free object and expect an error/no-arrays message
4. Real data: replace the Fictional Sample Payload code with your object of the same schema; no other code changes needed

Service Value

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