Score and route leads with Telegram alerts and Box storage
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 16 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Box and Telegram.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Normalize Lead Data (Edit Fields (Set)): sets or maps fields
- Validate Required Fields (Code): runs custom JavaScript code
- Merge: merges the data from its input branches
- Has Required Fields? (If): checks a condition and branches into true / false
- Calculate Lead Score (Code): runs custom JavaScript code
- Enrich with Clearbit (HTTP Request): calls an HTTP API
- Notify Marketing (Invalid Submission) (Telegram): uses Telegram
- Prepare Lead Record (Edit Fields (Set)): sets or maps fields
- Qualified Lead? (If): checks a condition and branches into true / false
- Build Lead JSON (Qualified) (Code): runs custom JavaScript code
…plus 5 more steps. See the full node list below.
Services it uses
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)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Box
n8n-nodes-base.box - Telegram
n8n-nodes-base.telegram
From the author
Lead Scoring Pipeline with Telegram and Box This workflow ingests incoming lead data from a form submission webhook, enriches each lead with external data sources, applies a custom scoring algorithm, and automatically stores the enriched record in Box while…