TradingView Webhook to cTrader
TradingView can send webhook alerts, but cTrader does not turn a webhook into a trade by itself. A reliable setup needs three parts: a TradingView alert, a routing layer that receives and validates the message, and a cTrader-side component that can execute the instruction.
NRUNO provides that route for cTrader traders: TradingView sends the webhook to your personal NRUNO URL, NRUNO processes the signal in the cloud, and the connected NRUNO cBot receives the instruction inside cTrader.
The practical signal path
- Your TradingView strategy or indicator triggers an alert.
- TradingView sends an HTTPS webhook request to your personal NRUNO URL.
- NRUNO validates the connector access and stores the event.
- The connected NRUNO cBot receives the instruction through the live connection.
- cTrader handles the order through your account and broker environment.
- The dashboard shows whether the signal arrived, was forwarded and received a response.
This matters because most failed automations are not caused by the idea of webhooks. They happen because the trader cannot see where the signal stopped.
What the alert message should contain
The exact format depends on your setup, but a useful alert message usually needs:
- action: entry, exit or management command
- side: buy or sell
- symbol: the instrument name as your broker expects it
- volume or risk value
- optional stop loss and take profit
- optional management mode such as break-even, Step trailing, FVG trailing or Hybrid Step + FVG
- a connector key or account-specific identifier
Do not include broker passwords, login credentials or private account data in TradingView alert messages.
Why a connector is needed
A webhook is only a delivery mechanism. It does not know your cTrader account, broker symbol mapping, risk settings or whether a signal should be tested in Paper mode first.
NRUNO turns the webhook into a cTrader workflow: personal endpoint, validation, logging, connected cBot and visible status. That is the difference between "an alert was sent" and "I can see what happened to the alert".
Testing checklist before live orders
Before live execution, test the full route with a small controlled setup:
- Confirm that the personal webhook URL is correct.
- Send a Paper-mode test alert.
- Check that the dashboard receives the signal.
- Check symbol spelling and broker suffixes.
- Confirm volume, SL and TP interpretation.
- Confirm exit behaviour if you use break-even or trailing.
- Switch to Live only after the route behaves as expected.
FAQ
Can TradingView connect directly to cTrader?
TradingView can send webhook requests, but cTrader needs a connector, cBot or API workflow to turn that message into an execution instruction.
Does NRUNO create the trading signal?
No. Your strategy and alert logic remain in TradingView. NRUNO routes the technical instruction.
Can NRUNO manage exits after entry?
Yes. NRUNO supports fixed TP/SL, break-even, Step trailing, FVG trailing and Hybrid Step + FVG in the cTrader-side workflow.
What if an alert does not arrive?
Start with the dashboard status. If no event appears, check the TradingView webhook URL and alert state. If the event appears but is not executed, check cBot connection, symbol, mode and account settings.