Safe Final Text Composer from Nested Objects

How it works

1. 1.Run the manual trigger; the first Code node emits three fictional items: plain text, a nested title object, and an item flagged to simulate an unserializable field
2. 2.Compose Final Text builds the throwing object locally, checks typeof for title/summary/status, builds final_text, and records composition_tags per part
3. 3.IF routes completed items to Label Completed Output and failed ones to Label Review Items with failed field names
4. 4.Merge (append, two separate inputs) joins both paths without dropping items
5. 5.Build Final Report produces a single report item with counters, IDs, and review details

Use cases

• Composing titles and summaries from heterogeneous JSON payloads with nested objects
• Sanitizing report lines before feeding templates or documents
• Triaging records needing human review before final line generation

Requirements

• n8n 2.46.6 with code, set, if, merge, stickyNote and manualTrigger nodes
• No credentials and no external calls whatsoever
• For real use: replace the sample generator with any source producing the same schema (id, title, summary, status)

Setup and testing in n8n

1. Import the JSON in n8n and execute the Manual Trigger
2. Verify item B-202's final text contains indented JSON of the object tagged «object» and no [object Object]
3. Verify C-303 is routed to review due to the simulated unserializable title field and the report shows 2 composed, 1 review
4. Edge test: empty the sample array (return []) to confirm empty-input handling

Service Value

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