Client Package Readiness Checker with Deduplication and Empty Batch Report

How it works

1. 1.Run the Manual Trigger to start the demonstration.
2. 2.Configure Required Fields defines mandatory company fields.
3. 3.Emit Sample Batch Envelope creates one envelope containing four fictional packages.
4. 4.Validate Normalize and Dedupe checks fields, emails, domains, and duplicate occurrences.
5. 5.Is Package Ready routes each result by its readiness condition.
6. 6.The two Set nodes add the route status while retaining all other fields.
7. 7.Merge Status Paths appends the two route outputs.
8. 8.Build Guaranteed Readiness Reports standardizes and sorts the final reports.

Use cases

• Auditing new client data before an agency project begins.
• Cleaning contact lists before transfer to another system.
• Detecting incomplete packages and batches containing no clients.

Requirements

• The manual demonstration requires no credentials.
• Real input must be one envelope containing a packages array.
• The source must emit the envelope even when packages is empty.
• Each client package uses company and contacts, with contacts containing name, email, and role.

Setup and testing in n8n

1. Import the JSON and run Manual Trigger; the four items should match expected_output.
2. Verify that [email protected] and [email protected] are one duplicate pair and the first is retained.
3. Verify that [email protected] remains in cleanContacts and is marked outside the domain.
4. Set packages in the sample node to [] while preserving the envelope; one needs-completion report should be emitted.
5. Try an empty or numeric email and confirm rejectedCount rises while countsBalanced remains true.

Service Value

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