Preflight Type Collision & [object Object] Risk Detector

How it works

1. 1.Run the Manual Trigger which emits an empty item
2. 2.A Code node emits the fictional test payload matching the real schema
3. 3.A depth-first Code node maps every full field path to observed types and record counts and flags danger
4. 4.A Set node formats a report line retaining all fields (includeOtherFields)
5. 5.IF routes dangerous paths (true) versus safe paths (false)
6. 6.Two NoOp branches feed a Merge node in append mode with inputs 0 and 1
7. 7.A final Code node aggregates all rows into ONE summary item with counters

Use cases

• Auditing heterogeneous API responses before writing string expressions
• Detecting per-field type collisions across records before full runs
• Documenting which fields will render as [object Object]

Requirements

• No credentials needed; all processing is local
• For real data replace the sample Code node with an HTTP Request or Webhook output of the same schema

Setup and testing in n8n

1. Import the workflow into n8n 2.45.7
2. Run the Manual Trigger and check the final summary: 10 paths, 4 dangerous, 6 safe
3. Verify age, meta, tags and tags[0] appear in dangerous with type_collision or implicit_object_to_string reasons
4. Remove the sample node and pass zero items to test the empty-input path

Service Value

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