For TradingView users
Execute your alerts
on crypto and MT5
TradingView is where a lot of strategies actually live. The gap is between the alert firing and an order existing somewhere real, and that gap is where sizing and risk belong.
- Webhook
- alert to live route
- Crypto + MT5
- the same alert can drive either
The flow
Alert in, checked order out.
Point the webhook
Your alert posts to a route URL. The message carries instrument and direction; nothing about size or risk comes from the alert.
Setup once
The route sizes it
Position size, mode and protection are route configuration. Change them without touching the Pine script.
Route config
The engine checks it
Daily loss, position cap, drawdown and cluster ceilings, evaluated before the order leaves.
Pre-trade
One alert, either venue
The same alert can drive a crypto exchange or an MT5 terminal. The strategy does not need to know which.
Venue-agnostic
The alert itself
What TradingView actually sends, and when.
Most of the difficulty in wiring an alert to an order is in the payload and the timing, not in the strategy.
Send JSON, not a sentence
Put a structured payload in the alert message — symbol, side, size and an id — rather than prose that has to be parsed hopefully. Placeholders like {{ticker}} and {{strategy.order.action}} are substituted by TradingView before it fires.
Payload
Once per bar, by default
A standard alert on a strategy fires at bar close, not on every tick. That is usually what you want, and it is why an alert can feel late against a chart you are watching live.
Bar close
The same alert can arrive twice
Webhook delivery is not exactly-once. Include a stable id in the payload and a repeat is recognised as a repeat rather than opening a second position.
Idempotency
Alert quotas are per plan
TradingView limits how many alerts you can keep active, and free plans are the tightest. One alert driving several accounts is usually better than one alert per account.
Per account
After the webhook
Where a chart signal stops being a chart signal.
The alert says what your indicator concluded. It does not know the size that fits your account, whether today has already lost more than you allow, or whether the symbol on the chart is the symbol your broker lists.
That mapping is the work. A TradingView symbol and a broker symbol frequently differ — the same instrument may be EURUSD on the chart and EURUSD.raw at the venue — so symbols are mapped per connection rather than passed through.
- Sizing computed against the account the route belongs to
- Limits evaluated at the moment the alert lands, not when the route started
- Symbols mapped per venue, so a correct alert cannot route to nothing
Send one alert at a demo account.
Fire an alert you already use into a demo route and watch it get sized, checked and either sent or refused.