Validate WhatsApp Lead Routing Rules in n8n (Synthetic Plans)

Validate your WhatsApp lead routing rules in n8n—before you send templates

This manual n8n workflow performs a local preflight to validate an agency lead-routing plan for WhatsApp template dispatch. It checks your route schema, match logic, and synthetic lead coverage, then returns a clear PASS or BLOCKED readiness receipt so you can fix issues before routing real leads.

What this workflow does

When you manually start the workflow, it:

• Loads a synthetic route plan containing route definitions, allowed match types, and example leads for test coverage.
• Validates the route plan schema, including required fields and structural correctness.
• Checks supported match types and evaluates whether match keys and match values align with your plan.
• Verifies E.164 recipient formatting for WhatsApp recipients used in the synthetic leads.
• Ensures placeholder values are replaced (for example, the Meta WhatsApp phoneNumberId placeholder) so the validation can succeed.
• Detects duplicate match keys and other blocking findings.
• Confirms each synthetic lead maps to exactly one client route—no missing routes, and no ambiguous routing.

Finally, it returns a receipt object with a readiness summary, detailed findings, and the recommended next action.

Use cases

• Preflight testing an n8n WhatsApp routing plan to prevent misrouted template messages.
• Quality checks when updating match types/values or client route codes—without touching real customer data.
• Debugging onboarding issues by running repeated synthetic validations until the workflow reports PASS.

Technical details

• Manual Trigger (run on demand)
• Code nodes to load and validate synthetic route plan data and recipients
• if logic for readiness decisioning (PASS/BLOCKED)
• sticky note for workflow documentation

Setup note: update “Load Synthetic Route Plan” with your intended route structure (match types/values, client codes, recipients, phone number IDs, template names, and language codes) using synthetic data only.