TradingView alerts to Telegram in under 2 seconds on Make.com

A registered research analyst in India now has every TradingView alert delivered to Telegram channels as a branded image in under 2 seconds, queued under Telegram's rate cap, deduplicated and running 24/7 on Make.com. Before this, each alert took two to five minutes of manual posting and overnight alerts did not go out at all.

A trading signal is worth less every second after the candle closes. Manual posting meant a designer or the analyst turned each alert into a branded image and pasted it in, with gaps overnight and during bursts, exactly when the signals mattered most. Two platform facts shape the design: TradingView drops a webhook if the receiver does not answer within about 3 seconds, and Telegram silently drops messages that exceed its per-channel rate limit. A pipeline that ignores either one loses alerts without telling anyone.

Two to five minutes per alert by hand, no coverage overnight, and during volatile sessions the post landed after the move. For a SEBI-registered adviser there is a second requirement: the registration number has to lead every message and send records have to be retrievable.

A webhook receiver that answers TradingView inside its 3-second window, then hands the payload to Make.com

Formatting from the alert fields, with a template per signal type: entries, exits and stop-losses each have their own layout, and the channel owner edits wording without touching the pipeline

A branded alert image rendered from the template

A queue that respects Telegram's cap of roughly 20 messages a minute per channel, so a burst is delivered in order rather than dropped

A dedupe key on every alert, so a retry never posts the same signal twice

A log line per run and a failure route that alerts the operator on a separate channel within seconds

TradingView fires the alert to the webhook URL with the symbol, price and action in the message.

The receiver acknowledges within the 3-second window and passes the payload on; nothing heavy happens before the acknowledgement.

Make.com picks the template for the signal type and fills it from the alert fields.

The branded image renders and the message, registration line first, joins the channel queue.

The queue posts through the Telegram Bot API under the rate cap, in order.

Each run writes a log line; a failure routes to the operator's alert channel with the payload attached.

Capture to channel post in under 2 seconds

100% coverage through volatile sessions, running around the clock since launch

Now offered as a fixed-scope bundle for other channel operators

The client called it "a lightning-fast, scalable system that saved us time and captured market momentum."

The client's five-star review is public on my Fiverr profile. The scenario canvas above is the live build, and the work is listed at nex-automations.com/work. The same design is sold as the TradingView to Telegram alert bot product on this profile, in three tiers, so the build is reproducible on request.

Research analysts, signal providers and trading communities that post TradingView alerts to Telegram, Discord or WhatsApp and are losing time or alerts to manual posting. Also anyone whose webhook source has a short timeout and whose destination has a rate limit.

TradingView fires a webhook, a receiver acknowledges it within 3 seconds, and Make.com formats and posts the message through a Telegram bot. Add a queue for Telegram's rate cap, a dedupe key and failure alerting, and it runs unattended in under 2 seconds per alert.

TradingView drops the alert if the receiver does not respond within about 3 seconds, and Telegram silently drops messages over its rate cap. The fix is to acknowledge first and process after, and to queue posts per channel.

Yes. Each signal type has its own template with the channel's branding and the registration line, and the image renders from the alert fields on every post. The Premium tier of the product on this profile includes per-signal image templates.

For a single channel with plain-text alerts at typical alert volumes, usually yes; that is the Starter tier. Image rendering, multiple channels and queues use more operations, so those tiers are sized to the buyer's alert volume before install.

Every alert carries a dedupe key built from its fields and timestamp. If TradingView or the queue retries, the key matches and the second post is skipped, so a retry never doubles a signal.

On this profile it is a product: Starter $49, Pro $249, Premium $499, with the scope of each tier listed on the product page. Custom builds beyond that are quoted fixed after a short call.

Prem Patel is the founder of Nex Automations, an automation studio based in India with 1,200+ automations in production for 210+ clients across 12+ countries over six years (figures from nex-automations.com, August 2026). Make.com Level 5 certified, the top of Make's certification ladder, and an official Make partner listed in the Make partner directory. Zapier Certified Expert and a listed Zapier Solution Partner. 5-star average across 94 public reviews on Fiverr and Topmate.

Website: nex-automations.com · LinkedIn: linkedin.com/in/iamprempatel

Last updated: 27 August 2026.