If your strategy already runs in TradingView, the missing piece is usually not another strategy. It is the technical path from an alert to an executable instruction at your broker.
TradingView strategies can simulate and backtest orders. TradingView’s own help center currently distinguishes that from automated strategy trading with a brokerage account. TradingView can, however, send webhook alerts to an external HTTPS endpoint. That makes it possible to connect a strategy event to an external execution system.
A typical workflow is: your Pine Script strategy or indicator creates the condition, TradingView triggers an alert, the alert sends a webhook, a connector validates and routes the message, and the execution component submits the instruction to the trading platform. With NRUNO, that route is TradingView → NRUNO Cloud → NRUNO cBot → cTrader.
The message should identify the intended action clearly. Depending on the setup this can include buy, sell, close, symbol, volume or risk, plus optional stop-loss and take-profit values. Broker passwords or other sensitive credentials should never be placed in the webhook body.
You can keep sending your own TradingView exits. Alternatively, the NRUNO cBot can apply local SL/TP, break-even, Fixed Distance trailing, 3-Step Pip trailing, FVG Structure or Hybrid Pip + FVG according to your settings.
Start in Paper Mode. Verify the alert event, exact message, symbol mapping, volume, spread filters, timing and exit behaviour. Only switch to Live when the same case behaves predictably. Automation can route instructions, but it cannot guarantee fills, liquidity or broker acceptance.
Official TradingView references: Pine strategy automation · Webhook alerts
Start in Paper Mode and verify the entire signal path before switching to Live.
Usually yes if it can create a suitable alert. Whether Pine changes are needed depends on what your current alert sends.
TradingView currently states that webhook alerts require two-factor authentication.
No. Your strategy or indicator remains responsible for the trading logic.
Not for NRUNO’s routing layer; NRUNO provides the webhook endpoint and cloud routing.