TradingView Webhook to Zerodha (India) — Setup Without Python

Why traders search for TradingView → Zerodha automation

TradingView is where many Indian traders research and alert. Zerodha Kite is where they execute. The gap is reliable delivery: copying alerts manually fails on fast markets, and writing a Python bot on a VPS is overkill for many retail users.

A webhook bridge receives TradingView’s HTTP POST when your alert fires, maps fields like symbol and action, and sends an order through your broker API — after you have connected Zerodha (or another supported broker) on the automation platform.

What you need before the webhook

A Zerodha account with API access enabled (Kite Connect where applicable).

An AlgoCrab account with Zerodha connected under Connect Broker.

AlgoCrab Bridge installed on a Windows machine that stays online during market hours (or a VPS running Bridge).

A TradingView alert on a strategy or indicator that supports webhook URLs (plan-dependent on TradingView).

High-level flow

1. Create a Bridge strategy card in AlgoCrab and note the webhook URL and secret.

2. Paste the webhook URL into your TradingView alert (Notifications → Webhook URL).

3. Use JSON in the alert message that Bridge understands — entry, exit, target, stoploss fields as documented in AlgoCrab Bridge help.

4. When the alert fires on a closed bar (or your chosen condition), TradingView POSTs to Bridge; Bridge validates and routes to Zerodha.

5. Confirm fills and rejects in AlgoCrab logs — never assume silent success.

Sample alert message shape (illustrative)

TradingView often sends plain text or JSON depending on your template. Bridge expects structured fields — check the latest Bridge signal documentation on AlgoCrab for exact keys. A typical pattern includes action (buy/sell/exit), symbol (NSE ticker format), quantity or product type, and optional target/stop points.

Avoid embedding secrets in the alert body; use the platform’s webhook URL authentication instead.

Common failures (and fixes)

Alert fired but no order: Bridge offline, wrong webhook URL, or Zerodha session expired — reconnect broker.

Symbol rejected: mismatch between TradingView symbol and broker symbol format (e.g. NSE:RELIANCE vs RELIANCE-EQ). Normalize in alert message or Bridge mapping.

Duplicate orders: use idempotency / signal IDs if your stack supports them; debounce repeated alerts on the same bar.

Paper vs live: confirm you are not still on a demo flag in Bridge or broker product type.

TradingView only vs coding on chart

If you only need alerts from TradingView, Bridge is the right tool. If a built-in strategy (SuperTrend, MA Cross, RSI and more) covers your rules, you can run it directly in Algo Trading without Pine Script.

Many traders combine both: research on TradingView, execution through Bridge; or built-in AlgoCrab strategies with no external webhook at all.

Compliance reminder

Automation must follow your broker’s API terms and applicable SEBI / exchange rules for your client category. Webhooks do not remove risk — test with minimum size first.