Alert Automation

Alert Automation is the simple way to turn your TradingView alerts into real orders on your broker accounts. Write a short alert in plain text, connect it once, and when your alert fires the order is placed — a single order, an option, or a full option structure you choose. Chartink support is coming soon and will work the same way.

You bring your own strategy and signals. The tool only places the orders you set up, and you can stop it at any time.

How it works

1. You create an alert in TradingView (from an indicator, a strategy or a price level).
2. TradingView sends that alert to your own private AutoTrader Web link the moment it fires.
3. AutoTrader Web reads your short alert, works out the exact order (including the option strike and expiry, if any), and places it in the account or group you named.
4. You can watch each alert move from received to placed on the Alert Trail screen.

Nothing runs unless your alert fires and you have set it up. You stay in control of every part.

Before you start

• A paid TradingView plan (webhooks are a paid feature).
• A registered AutoTrader Web account. Register here if you have not.
• At least one trading account added. See Trading Accounts.
• Optional: a group if you want one alert to trade many accounts. See Group Accounts.

Step 1 — Get your private webhook link

Sign in to AutoTrader Web and open Alert Auto. → Tokens from the left menu. Give the token a name and create it. This gives you a private link that looks like this:

https://signals.stocksdeveloper.in/tradingview/YOUR-TOKEN

• Keep this link private. It is the key that lets your alerts place orders in your account.
• You do not put your API key anywhere in TradingView. The link is all you need.
• If the link is ever exposed, open Alert Auto. → Tokens again, revoke it, and create a new one. Your old link stops working at once, and no one can use it again.

Step 2 — Create the alert in TradingView

1. Open your chart and add your indicator or strategy.
2. Create an alert (press Alt + A).
3. In Notifications, turn on Webhook URL and paste your private link from Step 1.
4. In the alert Message box, write your order in the simple format below.
5. Optional: also turn on Send email so you keep a copy of each alert for your records.

You can learn more from the TradingView alerts help.

Skip the typing — the Pine Script library

If you build your strategies in Pine Script on TradingView, you do not have to write the alert text by hand. We publish a free, open-source Pine library that builds a correct alert message for you — you call one function and pass the result to alert().

Add it to the top of your script:

//@version=6
import StocksDeveloper/StocksDeveloperAlerts/1 as atw

Then build and fire an alert wherever your signal triggers:

// Buy one lot of an at-the-money Nifty call when your signal fires
if longSignal
    alert(atw.option(symbol="NIFTY", exchange="NFO", producttype="NORMAL",
          tradetype="BUY", optiontype="CE", strike="ATM", expiry="weekly",
          account="MY_ACCOUNT", lots=1), alert.freq_once_per_bar_close)

Every function returns the alert text and you decide when to fire it, so you stay in control. The functions cover everything on this page:

Function	What it places
atw.equity(...)	a single stock or futures order
atw.option(...)	a single option order (pick the strike and expiry)
atw.order(...)	the full single-order builder (every field)
atw.straddle / strangle / bullCall / bearPut / bullPut / bearCall / ironCondor / ironFly(...)	a ready-made option structure
atw.leg(...) + atw.multiLeg(...)	your own custom multi-leg (up to 10 legs)
atw.riskLimits(...)	a risk limit to attach to any order (pass as risk=)

A few more examples:

// Stock order to a whole group of accounts
alert(atw.equity(symbol="SBIN", exchange="NSE", producttype="INTRADAY",
      tradetype="BUY", group="MY_GROUP", lots=1))

// Iron condor with your own daily-loss limit
alert(atw.ironCondor(symbol="NIFTY", exchange="NFO", producttype="NORMAL",
      account="MY_ACCOUNT", lots=1, width=8, wing=4,
      risk=atw.riskLimits(maxloss=10000)))

// Your own four-leg structure
legs = array.from(atw.leg("PE","ATM-2","SELL"), atw.leg("PE","ATM-6","BUY"),
                  atw.leg("CE","ATM+2","SELL"), atw.leg("CE","ATM+6","BUY"))
alert(atw.multiLeg(symbol="NIFTY", exchange="NFO", producttype="NORMAL",
      account="MY_ACCOUNT", lots=1, expiry="weekly", legs=legs))

The field names and values are the same as the plain-text format below, so use this page as the reference for every option. You still need a paid TradingView plan to send the alert (webhooks are a paid feature). You can view the library on TradingView here: StocksDeveloperAlerts.

Getting the Pine Script itself written

We help with our side of it — the alert format, what each field means, which values it accepts, and why an alert was refused. We are not set up to read or debug a whole strategy script, so our support assistant will tell you honestly instead of guessing.

For the strategy code itself, use an AI coding assistant (ChatGPT, Claude, Gemini, Copilot, or whichever you use) — and give it this page first, so it uses our real field names instead of inventing them. There is also a plain-text map of our whole documentation at stocksdeveloper.in/llms.txt that most AI tools can read in one go.

Ready-to-copy prompts, and what to check before you trade with the result, are in Can you help me write or fix my Pine Script or API code?

Whatever writes your script, check the alert message it produces in the alert checker below before you go live.

Writing an alert

An alert is just a list of settings, one per line, written as name=value. Field names are not case sensitive.

Here is a simple order — sell one lot of a Nifty put option at a limit price:

account=MY_ACCOUNT
symbol=NIFTY
exchange=NFO
producttype=NORMAL
optiontype=PE
strike=ATM
expiry=weekly
tradetype=SELL
ordertype=LIMIT
price=50
lots=1

Check it before you use it

Paste your alert below and it is checked straight away — the same required fields, the same allowed values and the same reasons for refusing it that apply when your alert really arrives. Use the buttons to load a working example of each kind.

The thing worth noticing: an alert is either accepted in full or refused in full. There is no half-placed order — a mistake costs you an order you never wanted, never a filled position you cannot protect.

Three mistakes that stop an alert before it starts

These are the ones we see most often. In each case the alert reaches us, but there is nothing in it we can read, so no order is placed. All three are one small edit in TradingView.

• A colon instead of an equals sign. Settings are written account=MY_ACCOUNT, never account: MY_ACCOUNT. A line with a colon is skipped, so an alert written that way is completely empty to us. Change every : to =.
• TradingView’s own message left in the box. A new alert starts with a default message like SBIN, 1 Crossing Up. That is a sentence, not an order — it holds no settings at all. Clear the Message box and write your own order there.
• The classic JSON message on a new webhook link. If your message starts with { and contains "command", that is the classic setup. It only works with a classic webhook link. On a webhook link you created in Alert Automation, rewrite the message in the format above — or point the alert back at your classic link.

Paste your alert into the checker above and it will tell you which one it is, in the same words we would.

Where the order goes: account or group

Every alert must say where to place the order, using one of these:

• account=NAME — place in that single account.
• group=NAME — place in every live account in that group.

Use exactly one. An individual account and a group can have the same name, so the field name is what tells us which you mean. There is no default — always say where.

The common fields

Field	Required?	What it is
account or group	Yes (one of them)	Where to place the order (see above).
symbol	Yes	The instrument — our broker-independent symbol (e.g. NIFTY, BANKNIFTY, SBIN) or your TradingView symbol. Look it up if unsure.
exchange	Yes	The exchange code, e.g. NSE or BSE for stocks, or NFO for options and futures. Look it up if unsure.
producttype	Yes	INTRADAY, DELIVERY, NORMAL or MTF.
tradetype	Yes	BUY or SELL.
lots or quantity	Yes (one of them)	Size — see Order size.
ordertype	No (default MARKET)	MARKET, LIMIT, STOP_LOSS or SL_MARKET.
price	No	Limit price (needed for LIMIT).
triggerprice	No	Trigger price (needed for stop-loss orders).
validity	No (default DAY)	DAY or IOC.
amo	No (default false)	true for an after-market order.

Use the exact words shown (for example INTRADAY, not your broker’s short form). For the full list of valid values, see API Parameters.

NFO and NSE mean the same market to us, so either one works for an option or a future — send whichever your chart uses. The same goes for the other segment codes: they are all read as the main exchange they belong to. This is why a message about a wrong exchange lists only the main ones.

Using your TradingView symbol

For a stock or futures order you can send TradingView’s own symbol, so your alert can simply use symbol={{ticker}}. AutoTrader Web reads these forms:

• a continuous future like NIFTY1! (nearest expiry) or NIFTY2! (next expiry);
• a dated future like NIFTYU2026;
• an option like NIFTY260714C23900.

Our own broker-independent symbol still works too — a future as NIFTY_28-JUL-2026_FUT, an option as NIFTY_14-JUL-2026_CE_23900, or a stock as SBIN. Either way, set exchange to match your instrument. If a symbol cannot be matched to a live contract, the alert is rejected with a clear reason — it never places a different order.

For options, the easy way below (give the underlier plus optiontype, strike and expiry) still needs no symbol lookup at all.

Trading options the easy way

For an option order you do not need to type the full option symbol. Give the underlier and let AutoTrader Web pick the exact contract:

Field	What it is
optiontype	CE for a call, PE for a put. Adding this makes it an option order.
strike	ATM (default), or ATM+1 / ATM-2 to step up or down, or OTM / ITM (add a number like OTM2), or an exact strike like 24500.
expiry	weekly (default), next (next weekly), monthly, or an exact date like 10-JUL-2026.

So optiontype=CE, strike=OTM2, expiry=weekly means “the call option two strikes out of the money in this week’s expiry” — no symbol lookup needed.

Ready-made option structures

You can build a full multi-leg option structure with a single line. You choose the structure and set the values; AutoTrader Web works out each leg for you and places them, with the protective buy legs placed first.

These build the order legs for a structure you choose and configure. They are not trading strategies, tips or advice — you decide the structure, the values and when to send the alert.

Structure	What you write	Legs it builds (by default)
Straddle	strategy=straddle	Buy call + buy put, at the money
Strangle	strategy=strangle	Buy call + buy put, out of the money by width
Bull call spread	strategy=bull-call	Buy call at the money + sell call width out
Bear put spread	strategy=bear-put	Buy put at the money + sell put width out
Bull put spread	strategy=bull-put	Sell put at the money + buy put width out
Bear call spread	strategy=bear-call	Sell call at the money + buy call width out
Iron condor	strategy=iron-condor	Sell call + sell put width out, buy call + buy put width+wing out
Iron fly	strategy=iron-fly	Sell call + sell put at the money, buy call + buy put wing out

Settings you can add:

• width — how far out of the money the near legs sit, in strike steps (default 2).
• wing — how far the protective legs sit, in strike steps (default = width).
• tradetype — BUY builds the structure as shown above; SELL flips every leg.
• onlegfailure — what to do if one leg cannot be placed: alert (default, tell you), cancel (undo the legs already placed) or continue (place the rest).

Example — a Nifty iron condor for this week:

account=MY_ACCOUNT
symbol=NIFTY
exchange=NFO
producttype=NORMAL
strategy=iron-condor
width=8
wing=4
expiry=weekly
ordertype=LIMIT
price=50
lots=1

Build your own multi-leg

If you want an exact set of legs instead of a ready-made structure, list them yourself. Each leg is Leg1, Leg2, and so on (up to 10), written as <CE|PE> <strike> <BUY|SELL> [xN], where xN multiplies the size for that leg.

account=MY_ACCOUNT
symbol=NIFTY
exchange=NFO
producttype=NORMAL
expiry=weekly
lots=1
Leg1=PE ATM-2 SELL
Leg2=PE ATM-6 BUY
Leg3=CE ATM+2 SELL
Leg4=CE ATM+6 BUY

Risk limits you set (beta)

You can add your own risk limits to an alert. These are limits you decide and set up.

Risk limits are in early beta. Right now they alert you by email — the tool does not square off, block or stop your trades automatically yet. Use them as warnings for now. See Risk Management.

Limit	What you write	What it is
Maximum day loss	maxloss=5000	A cap on the day’s loss for the account (in your account currency). You are alerted if the loss crosses it.
Square-off time	forceexit=15:15	An intraday time (24-hour HH:mm) by which you want the position closed.
Entry-time window	entrywindow=09:20-14:30	Only take entries inside this time window (24-hour HH:mm-HH:mm).
Block on expiry day	blockonexpiryday=true	Do not take new entries on the instrument’s expiry day.

You can set more than one on the same alert. As the feature leaves beta, these limits will begin to act automatically instead of only alerting you.

Set a target and stop-loss (auto-exit)

You can add a target and a stop-loss to any order. Once your order is filled, AutoTrader Web watches the live price for you and closes the position the moment your target or your stop-loss is reached — whichever comes first. You set the levels, and you can stop it at any time.

This is an exit you set on your own order. It is not a tip, a strategy or advice — you choose the target and the stop-loss, and you decide when to send the alert.

Give each level as a percent, as points, or as an exact price:

Setting	What you write	What it means
Target	target=2%	Book profit when the price moves 2% in your favour.
Target (points)	target=15pt	Book profit 15 points in your favour.
Target (price)	target=1560	Book profit at the exact price 1560.
Stop-loss	stoploss=1%	Limit the loss — exit when the price moves 1% against you.
Stop-loss (points)	stoploss=15pt	Exit 15 points against you.
Stop-loss (price)	stoploss=1480	Exit at the exact price 1480.
Trailing stop-loss	stoploss=15pt trailsl=5pt	Your stop-loss starts 15 points away and moves up in 5-point steps as the price moves in your favour. It never moves back.

• You can set a target only, a stop-loss only, or both. With both, whichever is hit first closes the position and the other is cancelled.
• Percent and points are measured from the actual fill price of the contract you bought or sold, and that is the same price the exit watches. If you trade options, please read the note below.

How a trailing stop-loss works

A trailing stop-loss is written as two settings together, and each does a different job:

• stoploss= is how far behind the price your stop stays — the gap.
• trailsl= is how much the stop moves each step, as the price goes your way.

trailsl= on its own is not accepted, and the alert is rejected before any order is placed. On its own it cannot say how far behind the price your stop should sit, and guessing that for you is how a stop ends up far tighter than you intended.

Worked example. You buy at 100 with stoploss=10pt trailsl=2pt:

Price reaches	Your stop-loss is
100 (your fill)	90
101	90 — not a full step yet
102	92
104	94

The stop moves in whole steps, and it only ever moves closer to the price — never back down.

You can write both settings in percent instead: stoploss=1% trailsl=0.5% works the same way. A percent is worked out from your fill price and then stays fixed, so on a fill of 100 a 0.5% step is 0.50 and stays 0.50 — it does not grow as the price rises.

A trailing stop-loss cannot be given as an exact price. trailsl= takes a percent or points only, because it describes a distance the stop moves, not a level it sits at. The level comes from stoploss=.

Trading options? Points follow the option price

This one catches people out, so it is worth reading once.

When you buy or sell an option, the price we watch is the option price, not the index price on your chart. So stoploss=55pt on an option means 55 points of the option price. It does not mean 55 points of the index.

The two are not the same size. An option close to the money usually moves about half a point for every one point the index moves, and an option further away moves less than that. So a 55 point stop-loss on the option needs roughly a 110 point move in the index before it is reached.

Here is what that looks like on an option you bought at 760:

You write	Price level used	Roughly what the index has to do
stoploss=55pt	705	move about 110 points against you
stoploss=2%	744.8	move about 30 points against you
stoploss=740	740	move about 40 points against you

If your exit is not firing when you expected, this is the first thing to check. Set a smaller point value, or use a percent so the level scales with the option price. Either way, the Alert Trail shows the exact target and stop-loss price the moment your exit is armed, so you can read the real levels there before the trade runs.

Example — buy one lot and set a 2% target with a 1% stop-loss:

account=MY_ACCOUNT
symbol=SBIN
exchange=NSE
producttype=INTRADAY
tradetype=BUY
quantity=1
target=2%
stoploss=1%

The exit runs on our servers, so it keeps working even if your chart or your computer is off. You can watch it on the Alert Trail: you will see the exit armed when your order fills, and fired when a level is reached.

A few things to know:

• The auto-exit is for the same day — it ends at the close of the trading day and does not carry to the next day.
• If you close the position yourself, or a risk limit closes it, the auto-exit simply stops — it never places a second order. The Alert Trail shows it as cancelled, so a closed position is the usual reason an exit never fired.
• If the price jumps past both your target and your stop-loss at once, the stop-loss is used (safety first).
• One position per instrument in an account is managed at a time. If you add to the same position with another alert, the newest target and stop-loss apply to the whole position, worked out from the new average price once the added order fills.
• Adding to a position by hand does not change the exit. Your target and stop-loss stay at the prices set when the exit was armed, even though your average price has moved. Send another alert with the levels you want if you need them recalculated.

Bracket and cover orders from an alert

The target and stop-loss above manage your position. There is a second way to protect a trade from an alert: place an AutoTrader bracket order, where the levels belong to the order itself.

Add variety= to the alert:

Value	What you get
variety=AT_BO	A bracket order — a target and a stop-loss, with optional trailing.
variety=AT_CO	A cover order — a stop-loss only, with optional trailing.
(nothing)	A plain order. Add target=/stoploss= for the position-level auto-exit above.

account=MY_ACCOUNT
variety=AT_BO
exchange=<exchange>
symbol=SBIN
tradetype=BUY
producttype=INTRADAY
quantity=10
target=10pt
stoploss=10pt
trailsl=2pt

These work on every broker we support, including brokers with no bracket order of their own. Your entry goes to the broker as an ordinary intraday order, and we watch the levels. Full details: Bracket & Cover Orders.

What is different from the auto-exit above:

• It follows your order, not your position. If you already hold the same stock, or you add to it by hand, the bracket still covers exactly the quantity this alert bought. The auto-exit above manages whatever the net position happens to be.
• Levels must be written with pt — rupees away from your entry price. A percent (2%) or an exact price (1560) is not accepted here, and the alert is refused with the reason.
• AT_BO needs both a target and a stop-loss. AT_CO needs a stop-loss and takes no target.
• producttype=INTRADAY is required, and the position is squared off automatically before the market closes.
• You can change the levels afterwards from the Positions tab in AutoTrader Web — the position-level auto-exit has no such screen.
• One per symbol per account, and the quantity must fit within the exchange’s maximum for a single order. A quantity that would have to be split is refused rather than half-protected.
• You must agree to a short set of terms once, before your first one. Pick AT_BO in the order window and follow the one-time opt-in.

Everything is checked before any order is placed, so a mistake in the alert costs you an order you never wanted — never a filled position with no protection.

Order size

Give the size in one of two ways:

• lots=1 — number of lots (for derivatives). AutoTrader Web works out the quantity from the lot size.
• quantity=50 — an exact quantity (for shares, or a whole number of lots for derivatives).

Use one or the other, not both. If an order is larger than the exchange’s single-order cap — the quantity freeze limit — AutoTrader Web automatically splits it into smaller orders for you, each within the limit. You do not need to do anything; each part shows separately on the Alert Trail.

See what happened — the Alert Trail

Every alert is recorded on the Alert Trail screen. For each alert you can see it move through clear steps — received, understood, checked, and finally placed — so you always know what happened and when. If a step fails (for example a wrong value), the trail shows where and why.

The trail shows that your order was placed. To see whether it filled, and your live position, check your order book and positions on the trading screen as usual.

Record when your alert fired

The time shown against an alert on your chart is the time the candle started, not the moment your alert fired. On a one-minute chart the candle marked 09:30 runs until 09:30:59, so an alert on that candle can fire at any second inside that minute. This is why an alert sometimes looks 20 or 30 seconds late when nothing is slow.

To see the real firing time, add TradingView’s built-in {{timenow}} value as one extra line in your alert:

account=MY_ACCOUNT
symbol=NIFTY
exchange=NFO
producttype=INTRADAY
tradetype=BUY
lots=1
timenow={{timenow}}

Your alert is kept on the Alert Trail exactly as it arrived, so you can read the value there and compare it with the time we received the alert. Two things to know:

• {{timenow}} is given in UTC. Indian time is 5 hours and 30 minutes ahead, so 04:00:25 means 09:30:25 India time.
• A time that lands exactly on :00 seconds is almost always a candle time, not a firing time.

Any extra line we do not recognise is simply ignored, so adding timenow is safe and never affects your order. If you want to dig further, see TradingView alert looks delayed or late.

Worked examples (with video)

Want to see the whole thing end to end? These step-by-step guides build a TradingView strategy, backtest it, then automate it with AutoTrader Web — each with a video walkthrough (Hindi):

• Moving Average strategy
• Supertrend strategy

What happens if…

…my alert fires twice. Two orders are placed. We act on every alert that reaches us and we cannot tell a genuine alert from a repeat, so a strategy that fires twice will trade twice. Test with the smallest size first.

…my alert never arrives. Nothing happens, and we will not know. We act only when an alert reaches us — we do not watch your chart or your strategy. An alert that expired, a limit on your TradingView plan, or an outage on their side all look the same from here: silence. Check the Alert Trail if you expected something and nothing happened.

…my alert arrives but nothing can be read from it. No order is placed, and the Alert Trail says exactly what was wrong with the message. This is the most common reason an alert “does nothing”, and it is almost always one of the three message mistakes. Nothing about your wallet, your licence or your broker is involved — the alert stopped while we were still reading it.

…my alert arrives late. It is still acted on, at the price available when it arrives — not the price when it was sent.

…an order is rejected by my broker. It is shown in the Alert Trail with your broker’s own reason. Nothing is retried automatically.

…I cancel an order that an alert placed. We do not place it again. Once an order has been sent, it is yours — cancelling it is a deliberate action and we do not work against it.

…someone else gets my private link. They can place real orders on your accounts with it. The link is not protected by your password or your login. If you think anyone else has seen it, create a new one straight away from the Alert Automation screen — the old one stops working immediately.

…I use copy trading. If an alert acts on a master account, the orders are copied to your child accounts in the usual way. A copied order reaches a child account a short time after the master, so in a fast market a child account’s order can fill for less quantity, or not at all.

…my Market Price Protection is switched off. Some brokers refuse plain market orders, so orders from your alerts can be rejected. Keep it switched on. If orders are not filling because the price band is too narrow, you can widen it by setting Market Price Protection to AGGRESSIVE — though a band that is too wide can be refused by some brokers instead.

Safe-use notes

• Stop your alerts when you are not using them. TradingView alerts and strategies keep running on TradingView’s servers until you stop them. If you forget, orders may keep getting placed.
• Test with the smallest possible size first, then increase slowly once you are confident.
• Avoid changing your alert or strategy settings during live market hours. TradingView can repaint a signal when you change settings, which can give unexpected results.
• Automation has its own risks. Make sure you understand how your alerts and strategies work before you rely on them.

Support for Alert Automation will keep improving as we learn what our users need. Share your feedback through our contact page.