Key Alias Unifier: Recursive Resolver with Canonical Field

How it works

1. 1.Run the manual trigger to emit the three fictional sample records
2. 2.Recursive search finds the first alias at any depth, returning value, matched_alias, found_path and resolved
3. 3.A Set node creates canonical_amount with includeOtherFields enabled
4. 4.An IF node routes records by the resolved flag
5. 5.Resolved records tagged 'resolved'; missing records have the misleading canonical removed and tagged 'missing_alias'
6. 6.Merge append recombines both branches so output count equals input count with per-record status

Use cases

• Unifying amount fields that change names across yearly exports
• Extracting a value nested in arrays and objects at any depth
• Isolating records missing every alias for review without misleading values

Requirements

• No credentials; fully self-contained
• To change aliases: edit only the ALIASES constant in the Code node
• For real input: replace the sample node with a source of the same shape

Setup and testing in n8n

1. Import the JSON into n8n and open the workflow
2. Run 'Manual Trigger' and verify exactly three output records
3. Check R-001 and R-002 carry canonical_amount, found_path and status=resolved
4. Check R-003 has no canonical_amount and status=missing_alias
5. Add a new alias such as price to ALIASES and rerun to confirm R-003 resolves

Service Value

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