Parallel Array Name Inference with Conflict Guard and Provenance Report

How it works

1. 1.Manual Trigger runs a Code node emitting fictional sample payload with two parallel array pairs plus edge cases
2. 2.A Code node infers names from the parent field, applies the Map-based conflict guard, and produces records, provenance, and conflict report
3. 3.A Set node with includeOtherFields keeps all fields; its single output fans out to both the IF gate and the guard-report branch
4. 4.The IF node compares unique names to total columns: match streams records, mismatch routes to a NoOp failure path
5. 5.A Merge appends both branches and a final Code node builds one unified report item

Use cases

• Naming analytics tool exports that arrive as unnamed cols/rows parallel arrays
• Preventing wrong column-to-row binding when unpacking multiple parallel arrays
• Auditing the origin of automatically derived field names before loading to a warehouse

Requirements

• n8n with standard code/set/if/merge/noOp nodes (validated against 2.44.6)
• No credentials and no external connections: runs fully locally
• To use real data: replace the payload-generator Code node with a real trigger carrying the same payload schema

Setup and testing in n8n

1. Import the JSON into n8n and open the workflow
2. Run 'Manual Trigger' and inspect 'Build Final Naming Report': validation_status=pass with 4 records
3. Verify provenance (9 names) and conflict report (3 adjustments: billing_amount_2, billing_date_2, billing_amount_3)
4. For the failure path: alter the sample so unique names fall below total columns so the IF routes to the NoOp
5. Confirm legacy_cols (non-array) is ignored and audit_cols (no rows) yields names but zero records
6. Verify the Set node fans out from a single valid output (index 0) to both the IF and Stream Guard Report

Service Value

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