Pick your action and levels; the tool writes the exact alert JSON the SignalForge EA accepts. Same fields as our documentation: breakeven, up to five take-profits, trailing stop, comment and account routing.
{}
Fields mirror our documented webhook reference. Multi-TP uses points from entry; fractions are of the initial volume (0.5 = 50%). Breakeven, multi-TP and trailing run independently. When any tpN is present, EA-level TP settings are ignored for that position.
Paste it as the message of a TradingView alert and point that alert's webhook to your SignalForge endpoint. The server authenticates the alert with your license, normalizes the fields, and the EA executes on your MT5 account. Typical round trip, measured in production: ~180 ms from webhook to EA, ~0.5 s to the broker-confirmed order.
Account routing must be a quoted literal: writing it with a Pine placeholder can format it with thousands separators and break the JSON. And once any tpN field is present, every TP level for that position comes from the alert, so half-written multi-TP payloads quietly drop the EA-side take profits.
Yes. Every field here is documented in our webhook reference and taken from it: action, symbol, lot, sl/tp in pips, close with optional side or percent, comment, breakeven (trigger and offset), up to five take-profits with fractions, trailing stop (trigger, distance, step) and the Auto-Trend interval placeholder.
No. It builds the text in your browser. Nothing is sent or stored; you copy the JSON into your own TradingView alert.
With the account in Pips mode, sl_price and tp_price values are read as pips distances, which is the usual trap when migrating from bridges that use absolute prices. This tool works in points/pips to match the default behavior.
Add the account routing field with the login as text. Without it, the signal is broadcast to every EA connected with your token.
Fourteen days free on the bridge, no card. Your alert, your strategy, executed on your MT5 account.
Start the free trial →