Automate
Turn a TradingView strategy into real orders
A Pine strategy on a chart cannot place an order. TradingView can only fire an alert, and an alert is an HTTP request to a URL — it carries no broker, no account and no authentication. Everything between that request and a fill is what this page is about, including the five places the path can stop and what each one says when it does.
Checked against Tradeus on 14 September 2026.
Before you start
- A working Pine strategy. Automation does not improve one — it executes it faster and more reliably in both directions.
- A TradingView account with 2-factor authentication enabled.
- A connected broker account: Tradovate, Rithmic or TradeLocker.
- A Tradeus plan that includes the TradingView webhook — Algo or Unlimited.
The numbers
- Time TradingView waits for the receiver
- 3 seconds, then the request is cancelled
- Ports it will post to
- 80 and 443 only
- IPv6
- Not supported for webhooks
- Account requirement
- 2-factor authentication must be enabled
- Strategies on Manual
- None — the webhook endpoint is not on that plan
- Strategies on Algo
- Three
- Strategies on Unlimited
- Unlimited
- Signals recorded
- All of them, including the refused ones, with the reason
- Sizing methods
- Signal, fixed, risk in dollars, risk in percent
Step by step
What to do, in order.
- 1
The alert fires and is authenticated
TradingView posts your alert message to the strategy's webhook URL, and the passphrase in the body is checked before anything else happens. A wrong passphrase is refused here, at the door, and is recorded as such. TradingView gives the receiver three seconds to answer and will only post to ports 80 and 443.
- 2
It is normalised and recorded
Ticker, direction and quantity are read out of the payload and the signal is recorded — whether or not anything trades. This is why "nothing happened" is almost always answerable from the event log rather than by guesswork: the record exists even when the trade does not.
- 3
Each subscription decides for itself
Every account following the strategy applies its own size, its own trading window and its own risk gates. One signal can therefore put one contract on an evaluation, four on a funded account, and nothing at all on a third that is outside its hours.
- 4
The order is routed, or parked
Automatic subscriptions route the order as soon as it clears the risk gates. Manual subscriptions park it as pending and wait for you — the number beside Strategies in the sidebar is how many are waiting. Submit routes it as it stands, discard drops it, and both are final.
- 5
The account's own limits get the last word
A lock on the account is checked after everything else, and it refuses the order rather than trusting the strategy that produced it. That ordering is deliberate: the limit exists precisely for the days the strategy is wrong.
What goes wrong
Named after the message you will see.
Each of these is a line from the event log or from TradingView, written as it appears — because that is the string you will paste into a search box at the moment you need this page.
“unknown endpoint”
The webhook URL is wrong, or the strategy was deleted. Deleting a strategy is the only way to stop its webhook accepting signals; pausing it makes the endpoint answer with a paused status instead of trading.
“outside the trading window”
The subscription only trades certain hours and this one arrived outside them. It is a subscription setting, not a strategy setting, so it can differ between two accounts following the same alert.
“signal is too old”
It arrived later than the subscription's age limit — a stale retry, usually. This is the guard that stops a queued alert from yesterday opening a position this morning.
“already at target position”
A position_size alert asked for a position the account already holds. Nothing to do, and that is correct — it is the duplicate-alert protection working, not a missed trade.
“no subscription” — the alert arrived and nothing traded
The strategy received the signal and no account was following it. Open the strategy, add the account, and re-send. This accounts for more first-run confusion than every other cause put together, because the webhook itself answers perfectly well.
“invalid passphrase” after everything worked yesterday
Somebody pressed New passphrase. The old one stops working immediately and the alert in TradingView still carries it. Copy the current message off the strategy into the alert again.
Questions
Asked before buying, answered either way.
Can a Pine strategy place real orders by itself?
No. Pine runs inside TradingView and has no broker connection. The most it can do is fire an alert, which is an HTTP request to a URL you choose — everything after that request is somebody else's software.
Why did my alert arrive and nothing trade?
Almost always because no account is subscribed to the strategy. The event log names the reason for every signal it refused, and 'no subscription' is the most common one by a wide margin.
Does automation make a losing strategy profitable?
No. It places a losing trade on every connected account exactly as reliably as a winning one. What it removes is the delay, the missed alert and the fat finger — not the edge, which either exists or does not.
Can I watch it for a while before letting it trade on its own?
Yes — set the subscription to manual. Signals are parked as pending and the count appears beside Strategies; you submit or discard each one. It is meant for supervising a new strategy rather than for holding a signal until it looks better, because the market keeps moving while it waits.
In the handbook
The reference pages behind the steps above — one thing each, in full.
- How a signal becomes an orderThe path an alert takes, and the two places it can stop.
- Automatic and manualThe confirmation queue, and the number on the Strategies tab.
- When a signal does not tradeRead the event log first — it names the reason.
- Position sizeFour methods, set per account and not per strategy.
Sources
Every claim above about somebody else's product, linked to the page it was read from. If one of them no longer says what this page says, this page is wrong and we want to know: tell us.
Checked against the live product on 14 September 2026. Broker screens and TradingView's own limits change; a step that no longer matches what you see is a step we need to fix.
Next
The neighbouring jobs.
Weighing this against another tool? All 5 compared, every row linked to the page it was read from.
The only step this page cannot do.
Everything above is mechanical and takes about ten minutes. Whether it behaves the way you expect on your own accounts is the part nobody can write down for you.