Execute TradingView alerts automatically from signal to cTrader by defining exactly which alert event represents the trade instruction. A precise event makes strategy logic, transport and broker execution easier to separate.
Alerts can originate from indicator conditions, alert() calls, strategy orders or other supported events. They may occur at different moments. Decide whether the external action should use an intrabar event, confirmed bar or strategy order event before connecting execution.
The receiver should not have to guess what the message means. Include an explicit action and the execution data needed by the workflow. Define close, partial close or reverse commands deliberately if you use them.
Realtime systems can encounter duplicate messages, reconnects or delayed events. A production connector should distinguish new instructions from previously processed ones and reject messages that are too old according to policy. Signal IDs and maximum signal age help.
The TradingView alert timestamp is not the broker fill timestamp. Webhook transport, validation, cBot processing, cTrader submission and broker handling happen afterward. Measure each stage separately.
Automatic execution needs a clear exit plan. Continue sending TradingView close events or use configured cTrader-side protection such as local SL/TP, break-even and trailing. Combine multiple exit systems only when their priority is understood.
Primary sources: TradingView webhooks · Webhook security
Only if it represents a supported instruction and the connector can interpret it.
Use instruction identity/state and make sure the alert logic does not emit the same event unintentionally.
No. Transport and broker processing happen afterward.
Yes, through TradingView close instructions or configured cTrader-side management.