Short answer: TradingView can place orders at your broker, but only the ones you click. You can connect a supported broker to the Trading Panel and trade manually from the chart. What TradingView cannot do today is run a Pine Script strategy and send its orders to your live broker account on its own. TradingView says so directly: "Automated strategy trading with a brokerage account is not available on TradingView yet."[1]
That single sentence is the source of most of the confusion. "My broker is on TradingView" and "my strategy trades automatically" sound like the same thing, and they are not. This article separates the three routes a trader can actually take, shows which one answers which question, and ends with a worked example for the common case: an MT5 account at a broker that also appears in TradingView's broker list. It is written for traders who already have a TradingView strategy or alert and want to know how it reaches a real account. If you only trade manually from the chart, Route 1 is all you need and you can stop after that section.
The three routes, in one sentence each
- Route 1: TradingView's Trading Panel. You connect a supported broker and place orders yourself from the chart or order ticket. Manual only.
- Route 2: alert → webhook → connector → MetaTrader terminal. Your strategy or indicator fires an alert, TradingView sends a webhook, and an external connector turns it into an order on an MT4 or MT5 terminal you (or a hosting provider) keep running. This is where PineConnector sits.
- Route 3: the strategy lives inside MT5. You rewrite the logic as an MQL5 Expert Advisor and it trades at the broker's MT5 server with TradingView out of the loop entirely.
Route 1: trading from the chart with a connected broker
TradingView's help centre describes this route plainly. On Supercharts you "click the 'Trade' button at the top toolbar" and "you'll see the list of licensed and verified brokers."[2] After logging in to a broker, you can "place a trade using different methods: via the order ticket, leveraging chart trading, shortcuts, and using more methods."[2] TradingView is explicit about its role: it "doesn't process your trades and acts as an interface only", and "all your broker credentials remain safe" with the broker.[2]
What this route does not include is automation. The same help centre states that "strategy trading is limited to the backtesting mode only."[1] A Pine Script strategy running on your chart is simulating fills against TradingView's broker emulator, not sending them to the account you connected in the Trading Panel. TradingView's broker directory lists dozens of integrated brokers including Pepperstone, OANDA, IC Markets, BlackBull Markets and ThinkMarkets,[3] and none of those integrations changes that limit, because the limit is on TradingView's side.
Choose Route 1 if you trade manually and want chart-based order entry at a broker TradingView supports. Choose something else if you want a strategy or indicator to place orders while you are away from the screen.
Route 2: alerts and webhooks to an MT5 terminal
This is the route TradingView's own documentation makes possible even though it does not describe the full chain. Alerts can be attached to a strategy's order events: "When an order placed by the strategy is executed by the broker emulator, an alert is triggered."[4] The alert message can carry order details through placeholders such as {{strategy.order.action}}, {{strategy.order.contracts}} and {{strategy.order.price}},[4] and the Pine documentation adds that scripts can set custom text per order through the alert_message parameter, surfaced with the {{strategy.order.alert_message}} placeholder.[5] One caveat worth knowing: "No alert-related Pine Script code can create a running alert in the charts UI"; you still create the alert by hand in the alert dialog.[5]
The alert then leaves TradingView as a webhook: "A TradingView webhook notifies your external app when an alert is triggered" by sending "a POST request to a URL you provide."[6] Three rules from that page shape everything downstream. The receiver must answer fast, because "if a remote server takes longer than three seconds to process a request, the request will be cancelled."[6] Delivery is not guaranteed: "Webhooks may occasionally fail to reach the specified URL."[6] And the message must not carry secrets: "Ensure that you don't include sensitive information such as login credentials or passwords in the webhook body."[6]
From the webhook onward, TradingView is finished. Something else has to receive the message, work out which account it is for, and place the order. With PineConnector, that "something" is two parts. The Bridge receives the webhook and routes it by the licence ID that leads every message; the format is fixed as LicenseID,Command,Symbol,Parameters and "the sequence (License ID, then Command, then Symbol, then any Other parameters) is mandatory."[7] A PineConnector Expert Advisor running inside an MT5 terminal then places the order at your broker. That terminal is the always-on part of the chain. MetaQuotes lists "turn off the trading platform" among the actions that stop an Expert Advisor,[8] so if the terminal is closed, asleep or rebooting, the alert arrives and nothing trades.
You have two ways to keep that terminal running. Self-hosted: MT5 and the PineConnector EA on your own Windows machine or a VPS, which the complete setup guide walks through. Hosted: PineConnector Edge, managed MT5 hosting included in every plan, where PineConnector runs the terminal and you control it from the portal. Edge is currently in early access, runs the PineConnector EA only ("Edge does not support custom or other third-party EAs"), and the guide recommends "using a demo account for your first setup and test trade."[9] PineConnector describes the arrangement as "managed infrastructure, not managed execution": the machine is theirs, the broker account, the strategy and every instruction remain yours.[10]
Choose Route 2 if you want to keep your strategy on TradingView and have its alerts executed on an MT4 or MT5 account. Choose something else if your broker offers no MetaTrader account, or you need logic that must react inside the terminal on every tick.
Route 3: move the strategy into MT5
The third route removes TradingView from execution altogether. You rewrite the strategy as an MQL5 Expert Advisor, backtest it again in MT5's own Strategy Tester, and run it in a terminal that connects directly to the broker's MT5 server. The terminal still has to stay on, so the hosting question is identical to Route 2, but there is no alert, no webhook and no three-second window. The trade-off is effort: two codebases if you keep charting on TradingView, or leaving TradingView behind. The rewrite-or-route comparison covers that decision in detail.
Note that PineConnector Edge does not host your own EA. If you take Route 3, you self-host.
Worked example: an MT5 account at a broker TradingView lists
Say you hold an MT5 account at a broker that also appears in TradingView's broker directory. It is natural to assume the two facts combine into automation. Here is what each route actually gives you.
| You want to… | Route | What happens | What stays yours |
|---|---|---|---|
| Click buy on the chart and see the fill in your broker account | 1 | Trading Panel sends the order; TradingView is "an interface only".[2] | Every click |
| Have your Pine strategy's orders reach that same account without you | Not 1 | Not offered: "limited to the backtesting mode only."[1] | n/a |
| Have the strategy's alerts executed on your MT5 account | 2 | Alert → webhook → PineConnector Bridge → EA in an MT5 terminal → broker's MT5 server | Strategy, broker login, every instruction; the terminal too unless you use Edge |
| Run the logic inside MT5 and drop TradingView from execution | 3 | Your MQL5 EA trades in a terminal you keep running | Everything, including hosting |
The broker appearing in TradingView's list matters for Route 1 only. For Route 2 what matters is that the broker offers MT5 and that the connector supports it. Check the broker's MT5 server availability before assuming anything, and test on a demo account first.
Where TradingView's documentation is silent
Two things are worth stating so you do not read more into the sources than they say. First, TradingView's "how to autotrade" page confirms only that automated strategy trading with a brokerage account is not available and that TradingView is "considering implementing this in the future";[1] it does not describe or endorse any external route. Second, the webhook and strategy-alert pages document the mechanism without naming any connector. Route 2 is an assembly of documented parts, not a TradingView feature, and the reliability of the assembly depends on the parts you choose and how you host the terminal. The stage-by-stage diagnosis shows what to check when an alert arrives and no trade follows.
Frequently asked questions
If my broker is integrated with TradingView, can my strategy auto-trade there?
No. Broker integration enables manual trading through the Trading Panel. TradingView states that "automated strategy trading with a brokerage account is not available on TradingView yet."[1]
Does an alert with a webhook place the trade?
The webhook only delivers a message to a URL you specify.[6] Something at that URL has to place the trade. With PineConnector that is the Bridge plus an EA running in an MT5 terminal.
Do I still need a computer on if I use PineConnector Edge?
No. PineConnector runs the MT5 terminal on its infrastructure and you control it from the portal.[9] Your TradingView alerts still have to be created and left active on TradingView's side.
Can I use TradingView's paper trading to test Route 2?
Paper trading tests Route 1's order entry against a simulator. To test Route 2 end to end, send an alert to a demo MT5 account and confirm the order appears on the intended account with the intended symbol, direction and volume.
Next step
If you want your TradingView alerts executed on an MT5 account, read the complete TradingView-to-MT5 setup guide, which puts the hosted-versus-self-hosted choice first and ends with a verified demo trade. For what the hosted option includes and excludes, see What is PineConnector Edge? and the Edge page.
Reviewed 10 September 2026. Facts and prices were checked against the linked sources on that date.
Sources
- TradingView Help Center – How to autotrade using Pine Script strategies, accessed 10 September 2026.
- TradingView Help Center – How to trade on TradingView, accessed 10 September 2026.
- TradingView – Top Brokers, accessed 10 September 2026.
- TradingView Help Center – Strategy Alerts, accessed 10 September 2026.
- TradingView Pine Script documentation – Concepts: Alerts, accessed 10 September 2026.
- TradingView Help Center – How to configure webhook alerts, accessed 10 September 2026.
- PineConnector Docs – Syntax, accessed 10 September 2026.
- MetaQuotes – MetaTrader 5 Help: How to Create an Expert Advisor or an Indicator, accessed 10 September 2026.
- PineConnector Docs – Edge (Early Access) guide, accessed 10 September 2026.
- PineConnector – PineConnector Edge: managed MT5 hosting, accessed 10 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
