TradingView webhook for MT4, MT5 and cTrader
TradingView can send an HTTP webhook when an alert fires, but it does not execute on MetaTrader or cTrader by itself. TheConnector receives the alert, checks the payload and routes the instruction to the selected account while keeping status history visible.
{
"account": "acct_mt5_8841",
"action": "buy",
"symbol": "EURUSD",
"volume": 0.10,
"sl": 1.0820,
"tp": 1.0910
}
What a TradingView webhook does
The webhook is the transport layer: it sends the alert message to a URL. Execution still depends on the bridge, the terminal, the broker and the account rules.
- ✓ TradingView fires the alert
- ✓ TheConnector validates the payload
- ✓ The terminal receives only its routed instruction
Recommended setup path
Start with one account and one readable JSON message. Add symbol mapping, SL/TP and multi-account routing only after the first route is visible in the dashboard.
- ✓ Create the account route
- ✓ Copy the per-account webhook URL
- ✓ Confirm history before increasing volume
MT4, MT5 and cTrader differences
The webhook format can stay stable, but each platform has its own terminal, permissions, symbols and execution constraints.
- ✓ MT4: EA permissions, AutoTrading and broker suffixes
- ✓ MT5: netting or hedging, filling mode and volume step
- ✓ cTrader: cBot or bridge, Automate permissions and symbol names
When comparing alternatives
Compare tools on the routes they cover, how clearly they show failures, and whether you can test safely before paying or moving a live account.
- ✓ PineConnector alternative pages should stay factual
- ✓ cTrader support is a separate decision point
- ✓ Late trading commands should expire, not replay