How to Automate TradingView Alerts in India (2026 Guide)

TradingView is where a huge share of Indian traders do their analysis — charts, Pine Script strategies, screeners, alerts. What it cannot do is place an order at an Indian broker when your alert fires. Some brokers support manual chart-trading inside TradingView, but a Pine strategy or indicator alert will not execute itself at Zerodha, Fyers or Dhan.

The missing piece is an execution layer, and the mechanism is the webhook: when a TradingView alert fires, it can send a message to a URL. Point that URL at a platform connected to your broker’s official API, and the alert becomes a real order — validated, risk-checked and placed in seconds. This guide walks through the full setup and the practical details that decide whether it works reliably.

What you need

1. A TradingView plan with webhook alerts. Webhook notifications are a paid-tier TradingView feature — check their current plans.
2. An execution platform connected to your broker’s official API. This is what INDfolio AI’s TradingView automation does for Zerodha, Fyers, Dhan, Angel One, Upstox, Alice Blue and Shoonya.
3. A broker API connection. Enabled once, from your broker’s console — see our setup guides for Zerodha, Fyers and Dhan.

That’s the whole stack. Older setups involved desktop “bridge” software running on your own PC or a rented VPS; cloud execution has largely replaced them because there is nothing to keep running at home — a laptop that sleeps mid-session cannot miss a signal it was never responsible for.

The setup, step by step

Step 1 — Create the automation on the execution platform. In INDfolio AI, you define what an incoming alert is allowed to do: the instrument, order type, quantity or capital-per-trade sizing, and the risk rules — maximum positions, daily loss cap, square-off time. The platform generates a unique webhook URL for the automation.

Step 2 — Create the alert in TradingView. On your chart or Pine strategy, create an alert as usual. In the alert dialog, enable the webhook notification and paste your automation’s URL.

Step 3 — Shape the alert message. The alert’s message field tells the execution platform what happened. For Pine strategies, TradingView placeholders do the work — {{strategy.order.action}}, {{ticker}}, {{strategy.order.contracts}} — so one alert handles both entries and exits. For simple indicator or price alerts, a fixed message (“BUY signal on RELIANCE”) mapped to a defined action works fine.

Step 4 — Test before trusting. Fire the alert against a paper-trading configuration first. You are checking three things: the alert reaches the platform, the platform interprets it as intended, and the risk rules behave — an alert that would breach your position limit should be rejected, not obeyed.

Step 5 — Go live small. Switch the automation to your live broker connection with minimum quantity, watch it through a few real signals, then scale.

The details that decide reliability

Latency is fine for most strategies — and wrong for a few. The alert → webhook → risk check → broker API chain completes in seconds. For intraday and swing systems, irrelevant. For strategies that depend on sub-second execution, alert-based automation is the wrong architecture; those belong as native strategies running against live market data.

Exits deserve as much automation as entries. The classic half-automated failure: entries fire automatically, exits stay manual, and one missed exit erases a month of edge. Automate both — or attach the stop-loss and target on the platform side so every entry carries its exit from birth.

Zerodha’s daily session refresh. Kite Connect requires a once-a-day login to refresh the API session. If the session lapses, alerts have nowhere to go. INDfolio AI prompts before market open; whatever platform you use, make this ritual unmissable.

Risk rules belong on the execution side, not in the alert. TradingView does not know your account state. Position limits, daily loss caps and square-off rules must live where the orders are placed, so even a misfiring alert loop cannot run through your capital.

One alert, one purpose. Resist stuffing multiple instruments or conditional logic into a single alert message. One automation per strategy per instrument keeps failures diagnosable and risk limits meaningful.

Is this legal in India?

Yes — when execution flows through a SEBI-registered broker’s official API with risk controls, alert automation sits inside the same framework as any retail algo. The execution platform and broker are the regulated path; TradingView is just the signal source. The setups to avoid are the ones that bypass official APIs (screen-scraping, session hijacking) — covered in detail in our guide to algo trading legality in India.

When to outgrow alert automation

Alert-based automation is the fastest bridge from analysis you already trust to execution you no longer do by hand. Its structural limits: TradingView cannot see your fills or account state, backtesting stays chart-based, and strategy logic lives in Pine.

When a strategy earns real capital, many traders rebuild it natively in INDfolio AI — described in plain English, backtested on NSE data with the full Indian cost stack, stress-tested with Monte Carlo simulation, and run entirely in the cloud. The webhook path stays available for everything still living on your charts; there is no forced migration.

Frequently asked questions

Can TradingView place orders directly at Indian brokers? Manual chart-trading, with some brokers. Automated strategy execution, no — Pine strategies and alerts need an execution layer connected to a broker API.

Do I need a paid TradingView plan? Webhook alerts are a paid-tier feature per TradingView’s plans. The free tier’s app/email notifications cannot trigger automation.

Which Indian brokers can receive automated TradingView orders? Through INDfolio AI: Zerodha, Fyers, Dhan, Angel One, Upstox, Alice Blue and Shoonya — via each broker’s official API.

What happens if my alert fires when markets are closed? A sane execution platform validates before placing: market-closed alerts are rejected or queued per your configuration, and risk rules apply either way.

Can I automate Chartink scanners the same way? Yes — the same webhook pattern works for Chartink scanner alerts. See Chartink automation.