Hi everyone! I wanted to share a workflow I built to solve a common problem: fragmented user identity across multiple channels.
The goal was simple: make sure a user remains the same person inside the system, even if they switch between WhatsApp, email, Telegram, or other channels.
No more duplicated users.
No more restarting onboarding from scratch.
Key features of this workflow:
Omnichannel Identity Detection: Automatically detects the incoming channel and links the user to a single unified identity.
OTP Generation & Validation: Creates secure OTP codes with real expiration logic and validation handling.
Persistent Session Management: Maintains onboarding sessions so users don’t lose progress.
Centralized Database Logic: Uses Postgres (Supabase) to manage identity, verification status, and session continuity.
The workflow is designed to be modular and scalable, so it can be integrated into existing onboarding or customer support automations.
Important:
Along with the workflow, you’ll also need to download and create the required database tables in Supabase for everything to function correctly.
I’ve documented the full logic, architecture decisions, and implementation process in my blog.
You can explore the workflow and get the full template here:
[n8n template link]
Happy to answer any questions about the setup or architecture!