Route Facebook Story replies to Slack, Telegram, and Supabase CRM by region
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Telegram, Slack and Supabase.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Normalize Story Reply Payload (Function): runs custom JavaScript (legacy Function node)
- Insert Story Reply into Supabase (Supabase): uses Supabase
- Time-Zone Router (Function): runs custom JavaScript (legacy Function node)
- Assignment Successful? (If): checks a condition and branches into true / false
- Update Supabase – Assigned (Supabase): update
- Update Supabase – Unassigned (Supabase): update
- Telegram: uses Telegram
- Telegram: uses Telegram
- Slack: uses Slack
- Slack: uses Slack
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Normalize Story Reply Payload, Time-Zone Router: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Normalize Story Reply Payload, Time-Zone Router | Code node, mode 'Run Once for All Items' |
Nodes used (6)
- Webhook
n8n-nodes-base.webhook - Function
n8n-nodes-base.function - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - Slack
n8n-nodes-base.slack - Supabase
n8n-nodes-base.supabase
From the author
Facebook Story Replies → Telegram “Human Required” Routing + Supabase CRM This workflow automatically captures Facebook Story replies, normalizes incoming webhook payloads, stores them in Supabase, assigns them to the correct regional support team based on…