How do you get TradingView alerts into Telegram in under 2 seconds, 24/7, without losing or doubl...How do you get TradingView alerts into Telegram in under 2 seconds, 24/7, without losing or doubl...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
How do you get TradingView alerts into Telegram in under 2 seconds, 24/7, without losing or doubling a signal? The pipeline is easy to describe and hard to keep alive. Four traps decide it.
The shape: TradingView fires a webhook, Make.com catches it, formats the message the way the channel wants it, and posts it. Capture to post in under 2 seconds, around the clock, no human in the loop. That is the scenario in the image, running for a registered research analyst since 2025.
1. The 3-second window. TradingView gives a webhook receiver about 3 seconds to respond. A slow receiver loses the alert and nothing anywhere tells you. Fix: acknowledge instantly, process afterwards, never inline.
2. Telegram's rate cap. A channel takes roughly 20 messages a minute. One volatile candle across several symbols can fire more than that, and the extras vanish silently. Fix: a per-channel queue that preserves order and releases under the cap.
3. Duplicates. Retries and repeated triggers post the same signal twice unless every alert carries a dedupe key. Two identical entries in a row is how a channel loses trust in one afternoon. Fix: a key built from symbol, signal and bar time, checked before every send.
4. Silent death. The worst failure is the pipeline stopping while you assume it is posting. Fix: every run logged, every failure alerting you on a separate channel within seconds, and a heartbeat so silence itself raises an alarm.
One more for Indian channels: if the channel belongs to a SEBI-registered adviser, promotional messages need the registration number leading the message and you need retrievable send records. That is a formatting and logging problem, so the pipeline handles it.
Branded alert images instead of plain text are the same pipeline with one extra step: an image engine lays the signal over a base card by URL, so every alert ships as a picture. That build is its own case study on my profile.
The full case study is on my profile, and the delivered version (I install it on your Make.com account, with your templates, queue, dedupe, alerting and a send log) is the TradingView product on my services page.
Prem Patel, Nex Automations. Make.com Level 5 certified, official Make partner, Zapier Certified Expert.
Post image
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started