Seeing a broker in TradingView’s trading panel and automating a Pine strategy are two different problems. A broker integration may support manual chart trading without automatically executing your strategy alerts. connect a TradingView strategy to your broker here means connecting the full technical path from TradingView to execution in a controlled way.
A direct broker integration may let you place supported orders from TradingView’s interface. That does not automatically mean a Pine strategy can send simulated orders to the live account. For automation, you need a defined path from the strategy event to the broker-side execution platform.
TradingView can send an HTTP POST when an alert triggers. A connector can receive the message, validate it and pass an instruction to the execution platform. NRUNO uses this model for cTrader: TradingView → webhook → NRUNO Cloud → cBot → cTrader.
NRUNO does not independently integrate every broker API. Its current route is based on cTrader. Compatibility therefore depends on whether the account you want to trade is available in a compatible cTrader environment.
A TradingView symbol may not match the broker’s cTrader symbol exactly. Brokers can also impose different volume steps, minimum sizes, stop distances and market hours. These rules must be tested with the actual account.
Webhook messages should contain trading instructions, not account passwords. TradingView’s guidance warns against including sensitive information in webhook bodies.
Official TradingView references: Pine strategy automation · Webhook alerts
Start in Paper Mode and verify the entire signal path before switching to Live.
No. Manual broker integration and automated strategy execution are separate capabilities.
NRUNO’s current path is based on cTrader, so compatibility depends on the account being available there.
Symbol names, suffixes, volume rules, trading hours and minimum stop distances can differ.