Create a two-way WhatsApp + Telegram integration for 10k+ customer support chats
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 18 nodes and runs on WhatsApp events (messages) (plus 1 other trigger). Along the way it connects Telegram, Supabase and WhatsApp Business Cloud. It also calls api.telegram.org over HTTP.
How it runs
Trigger: On WhatsApp events (messages) (plus 1 other trigger).
- Get existing customer details (Supabase): get
- Filter messages that are replies in topics (Edit Fields (Set)): sets 2 fields: superGroupID, message
- Merge: merges the data from its input branches
- If: checks a condition and branches into true / false
- Set Telegram SuperGroupID (Edit Fields (Set)): sets 1 field: superGroupID
- Get a row (Supabase): get
- Get customer by phone (Supabase): get
- Customer Details (Edit Fields (Set)): sets 2 fields: customerName, CustomerPhone
- Send message (WhatsApp Business Cloud): send
- Merge: merges the data from its input branches
…plus 6 more steps. See the full node list below.
Services it uses
HTTP calls to: api.telegram.org
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - Edit Fields (Set)
n8n-nodes-base.set - Supabase
n8n-nodes-base.supabase - WhatsApp Business Cloud
n8n-nodes-base.whatsApp - If
n8n-nodes-base.if - Merge
n8n-nodes-base.merge - WhatsApp Trigger
n8n-nodes-base.whatsAppTrigger - HTTP Request
n8n-nodes-base.httpRequest
From the author
⚡ Next-Gen Customer Support: Two-Way WhatsApp + Telegram Integration for 10k+ Clients ------------------------------------------------------------------------ Who is this workflow for This workflow is designed for customer support teams, e-commerce founders,…