NRUNO Trading Automation Wiki · Question 9

Can Pine Script send trades to cTrader?

Getting Started & ArchitectureLast reviewed: 25 Aug 2026
Short answer

Pine Script supplies signal logic and alert messages; live cTrader execution happens outside Pine through TradingView alert delivery and an execution layer.

What this means in practice

Pine Script supplies signal logic and alert messages; live cTrader execution happens outside Pine through TradingView alert delivery and an execution layer. This page is specifically about “Can Pine Script send trades to cTrader?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — alertcondition()

Confirm that alertcondition() becomes true on the live bar and that the alert was recreated after relevant script or input changes. Dynamic order details that were never placed in the message cannot be reconstructed safely downstream. For Scenario A — alertcondition() on question 9, use that evidence specifically to answer “Can Pine Script send trades to cTrader?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — alert()

Inspect the exact runtime message emitted by alert(). Validate action, symbol, size, optional protection and signal ID; a correct Pine condition is not enough if the payload itself is incomplete. For Scenario B — alert() on question 9, use that evidence specifically to answer “Can Pine Script send trades to cTrader?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Strategy alert

Identify whether the strategy alert is driven by alert(), order fills, or both. A correct Strategy Tester result does not prove that the external alert instance sends the command you intend. For Scenario C — Strategy alert on question 9, use that evidence specifically to answer “Can Pine Script send trades to cTrader?”; keep it separate from the evidence for the other scenarios on this page.

Scenario D — Order-fill event

An order-fill alert is produced when TradingView's strategy emulator records a fill, not necessarily when the original condition first becomes true. Compare strategy fill time, alert time and payload, and verify settings such as process_orders_on_close and calc_on_order_fills. For Scenario D — Order-fill event on question 9, use that evidence specifically to answer “Can Pine Script send trades to cTrader?”; keep it separate from the evidence for the other scenarios on this page.

What to check

  • active server-side TradingView alert instance
  • saved symbol, timeframe and inputs
  • realtime versus confirmed-bar behavior
  • exact message emitted by the active alert

Practical rule

For “Can Pine Script send trades to cTrader?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.

Decision summary

Direct answer: Pine Script supplies signal logic and alert messages; live cTrader execution happens outside Pine through TradingView alert delivery and an execution layer.

Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.

Primary sources

Need a TradingView → cTrader execution route?

NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.