Supported signal text

The built-in Current parser reads structured trade text and supported follow-up commands. It does not promise to understand every message layout. Use Trading Profiles → Preview signal with actual examples from your source before applying a configuration.

All prices, distances, and volumes below are syntax illustrations only. They are not suggested trade settings or current market prices.

Basic entry with price targets

XAUUSD BUY @2500
SL 2490
TP1 2510
TP2 2520
TP3 2530

The symbol can appear before or after BUY/SELL. Numbered TP labels keep their target indices even when written in a different order. Five-target profiles can use TP1 through TP5; reading additional targets does not make them executable beyond the profile's supported target count. Inspect warnings and the actual preview plan.

Pending entries and explicit lots

Sell Limit EUR/USD
Entry: 1.09200 - 1.09300
S/L: 1.097
Take Profit: 1.084
0.10 LOTS

This identifies a sell-limit signal with two entries. EUR/USD is normalized to EURUSD before broker mapping. Whether the second entry creates another order depends on the profile's order layout and second-entry setting. An explicit lot also interacts with single-order versus TP-specific sizing; see Risk & order sizing.

The parser also recognizes supported BUY STOP, SELL STOP, BUY LIMIT, and SELL LIMIT text. Broker quotes, stop rules, and pending-order requirements still determine whether the resulting order is accepted.

Market signal with pip distances

GOLD BUY NOW
Stop Loss: 25 pips
TP1: 50 pips
TP3: 100 pips

A market message can omit a numeric entry. Explicit pips units remain distances rather than absolute prices. A missing TP2 stays missing; TP3 is not renamed TP2. Mapping and profile SL/TP rules are applied before broker validation.

Reply commands

Reply to the original tracked signal to identify its trade group. Supported built-in phrases include close, cancel, layer, layer now, move sl entry, and move sl to entry. Customize supported phrases in the profile's Command phrases section.

The built-in parser also understands structured RFC-prefixed commands. RFC is a command grammar, not a separate promise to read arbitrary source formats. Examples sent as replies to the original signal include:

Text	Meaning
RFC UPDATE SL TO 2500	Request a stop-loss update.
RFC UPDATE TP2 TO 2520	Request an update to TP2.
RFC CLOSE	Request a full close of the referenced trade scope.
RFC CLOSE HALF	Request a half-volume close in that scope.
RFC CLOSE TP2 35%	Request a partial close for the referenced TP2 leg.

Parser support does not bypass account permissions, ownership checks, profile/runtime restrictions, broker rules, or confirmation checks. Telegram command support is also separate from which manual controls are exposed in the dashboard.

Edits to the original message

An edit containing valid SL/TP changes is treated as an update to the original tracked signal, rather than a fresh entry. For example, an edited TP2: 0 explicitly requests clearing that target; an omitted target is different from an explicit zero.

Editing an original message into RFC CLOSE ALL, RFC START, close, or layer now is not treated as a newly executable command. A message sent as a reply is not silently converted into a fresh opening signal when its reply wording cannot be recognized. An edited reply is also not treated as a new entry.

When text cannot be used

Avoid malformed numeric fields such as @2500abc, SL 2490USD, or SL 10%. Clearly label entries and targets rather than relying on unrelated numbers in commentary. A parsed signal may still be skipped because its effective stop/target is missing, a filter blocks it, its symbol is unavailable, or the broker rejects the plan.

Use text replacements and AI recognition for unfamiliar source wording, then preview again. These examples document text parsing; they do not establish image/OCR support or that several independent trades in one message will all be executed.