Parallel Array Name Inference and Alignment Registry

How it works

1. 1.Run the manual trigger; the first Code node emits an equal-length payload (payload-A) and a mismatched one (payload-B)
2. 2.The second Code node deep-scans, infers array names from the parent field, and builds an alignment registry of name, length, path
3. 3.An IF node checks lengthsEqual and branches
4. 4.On success a Code node emits one row per index up to the shortest length, fields named from array names, not positions
5. 5.A Set node adds alignmentVerified while retaining all fields
6. 6.On mismatch a Set node tags status, then a NoOp node holds the case
7. 7.A Merge node unifies both branches into one output

Use cases

• Converting nested JSON with parallel arrays into stable named records
• Detecting parallel array length mismatches before row generation
• Documenting array structure when field order shifts between payloads

Requirements

• n8n 2.44.4 with built-in nodes only
• No external credentials
• To replace the demo: swap the payloads array in the emit Code node for real payloads of the same schema

Setup and testing in n8n

1. Import the JSON into n8n and execute the manual trigger
2. Verify the three named rows for payload-A in the final output
3. Verify payload-B reaches the mismatch path with status=held_for_review
4. Reorder array fields in a payload and confirm output names stay identical
5. Try a payload with empty arrays and confirm safe handling with zero rows

Service Value

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