How to Run a Pine Script Indicator on TradingLead

This guide shows how to take a Pine Script indicator — your own or one you have permission to use — and run it on a TradingLead chart, for example a Nifty 50 stock on a 15-minute chart.

Before you start, one honest note: TradingLead supports a documented Pine v5/v6 indicator subset. Source is validated before execution. Many common indicators run directly, some run with small visual differences, and some need changes. Studio tells you which before anything touches your chart.

Step 1: Open a chart

Go to tradinglead.in/charts, sign in, and load the symbol and interval you want. The indicator will be calculated on the candles this chart has loaded from its data feed.

Step 2: Open Indicator Studio in TLScript-Pine mode

Select the Indicator Studio tab in the bottom panel. Choose TLScript-Pine as the language. You can dock Studio below or beside the chart, or pop it out to its own window if you have a second screen.

To start from a blank guided template instead of pasting, click New — it inserts only guidance comments starting with //@version=6.

Step 3: Paste your script

Paste the full source. It must begin with a version line:

//@version=6
indicator("EMA trend", overlay=true)
length = input.int(20, "Length", minval=1)
src = input.source(close, "Source")
plot(ta.ema(src, length), "EMA", color=color.teal)

Scripts with //@version=1 to 4, an unknown future version, or no version line are rejected.

Step 4: Read the compatibility label

As soon as you paste, Studio checks the source locally and shows one label:

Common reasons for Unavailable:

• request.financial, request.earnings, request.dividends, request.splits, request.economic, request.currency_rate, request.seed or request.quandl — TradingView-hosted data services.
• import user/library/1 — published TradingView libraries are not fetched. Copy the functions you need into your script.

request.security is fine on charts: it reads other symbols or timeframes from the same authorized data feed.

Step 5: Fix problems (optionally with AI)

Every problem in the Problems list shows its line and column. Click one to jump to it.

If you want help from an AI assistant:

1. Click Copy fix prompt. Studio builds a prompt from the exact problems and your current code. Nothing is sent anywhere automatically.
2. Paste it into the AI you use and copy its answer (a full replacement script or SEARCH/REPLACE blocks).
3. Click Paste AI fix and paste the answer. Studio shows a preview, re-checks compatibility and compiles it in the sandbox.
4. Accept the fix. It updates only your unsaved draft — not the chart, not your library.

Step 6: Compile and Apply

• Click Compile to check the source against the runtime. Nothing changes on the chart yet.
• Click Apply to add the indicator to the active chart. Studio reports progress through preparation, history, calculation and drawing.

If you select an indicator that is already on the chart, the button becomes Review update, which shows the source/input changes and replaces only that instance.

Step 7: Adjust inputs and style

Your input.* declarations become a settings form. group creates sections, inline puts related inputs on one row, and tooltip adds help. Style-only changes (colour, width, visibility) don't rerun the script; input changes recalculate it. Settings stay open while you click the chart, so you can compare.

Step 8: Save it

Click Save (or Save as for a copy). The source and input values go into your library. Saving never changes what is applied on the chart, and applying never saves.

Your saved indicator now appears in the chart's Indicators dialog under My saved indicators, so you can add it to any chart like a built-in indicator. To move scripts to another browser, use Export library backup and Import library backup in the Library panel.

Tips for Indian markets

• ta.vwap resets on each exchange trading day, which suits intraday NSE/BSE charts. See VWAP.
• For Indian cash equities and indices in the built-in catalogue, syminfo.currency is INR.
• Test indicator ideas candle by candle with bar replay before relying on them.

Troubleshooting

• "Chart not ready" — wait for the chart to finish loading, then Apply again.
• Timeout — each operation has a 30-second limit; very heavy loops (over 20,000 iterations per loop) fail explicitly. Simplify the calculation.
• Strategy script — Pine strategies run through backtesting. See Backtest a Pine strategy.
• Alerts — alertcondition events stay local. You can hand a condition to the Alerts panel as a local rule evaluated while the app is open; push, email and webhook delivery for indicator conditions are not available.

Indicators are tools for analysis, not trade recommendations.