Nested JSON Field Pruner with Deletion Audit Trail

How it works

1. 1.Manual Trigger starts the run.
2. 2.Code node emits three fictional cases.
3. 3.Code node validates paths, prunes a deep copy, logs removed/missing paths.
4. 4.Set node adds status and removedCount.
5. 5.IF splits valid from rejected configs.
6. 6.Rejected branch is marked deletion_skipped.
7. 7.Merge appends branches; final Code builds one summary.

Use cases

• Strip volatile fields before deduplication or comparison.
• Remove internal fields before local archiving.

Requirements

• No credentials; replace the sample node with a source providing caseId, paths and record.

Setup and testing in n8n

1. Import and execute manually.
2. Check customer.internal and debugInfo on orders 0 and 2 are removed.
3. Check REC-003 is rejected with nothing deleted.
4. Try an empty segment or non-object record to see rejection.

Service Value

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