Quick Create — NLP Expression Reference

Type natural language or structured dot-notation to instantly build trading signal expressions.

1. Basic Syntax

Expressions follow the pattern: LEFT   OPERATOR   RIGHT with optional symbol and timeframe.

bullish engulfing > 0                 // unary — candle / pattern flag (compare > 0)
doji > 0 15min
RSI(14) < 30
SMA(50) > SMA(200)
Close > SMA(200) 5min

2. Canonical Generation Rules

When an AI/model generates expression JSON or dot-notation from this page, use these rules first.

3. Indicators

Regular Indicators — GTSIndicators (RSI · SMA · MACD · ...)

Use NAME(param) or NAME(p1,p2,p3) syntax. Subfields use .SubField.

MACD(12,26,9).Signal > 0         // MACD signal line
BBANDS(20,2).Upper > Close        // Bollinger upper band
STOCH(14,3,3).SlowK < 20        // Stochastic %K
ICHIMOKU.Tenkan > ICHIMOKU.Kijun  // Ichimoku crossover

Timeframes — how to add one

Append a timeframe token at the end of the expression. With no timeframe, the expression runs on whatever frame the alert/strategy is configured for. (Full token list in §10 Timeframes.)

RSI(14) < 30 5min            // 5-minute RSI
EMA(50) > EMA(200) 1h        // hourly EMA cross
SMA(200) > Close Daily        // daily SMA
MACD(12,26,9).Signal > 0 15min    // 15-minute MACD signal
ATR(14) > 5 4h               // 4-hour ATR

Symbols — with vs without

Expressions are symbol-agnostic on Trading — the symbol is bound by the strategy/handler at deploy, not on the expression. Write just the condition (and an optional timeframe); don’t add on SYMBOL.

// WITHOUT a symbol — runs on the configured symbol(s)
RSI(14) < 30
RSI(14) < 30 5min

// WITH a symbol (typical for alerts) — name the market, then the frame
RSI(14) < 30 5min
Close > SMA(200) 1h

Different notations

The same signal can be written in plain formula or in structured dot-notation.

All GTS Indicator Categories

Extended Indicators (200+) — ExtendedIndicators

Advanced / subsystem indicators (adaptive smoothers, SMC-ICT structure, ML / regime). Use NAME(param) syntax in natural/formula input; use ExtendedIndicators.NAME... in dot notation. Each indicator exposes named subfields such as .signal, .value, .trend, .upper — use only the subfields listed for that indicator.

AdaptiveMacdR2(20,12,26,9).signal > 0       // native MACD-style signal
QuantileVolatilityBands(100,2).upper > Close // upper volatility band
InertialStochastic(5,34,3,3).signal < 20 // native stochastic-style signal
BreakOfStructure(5,5).signal != 0       // structure break event

Extended Indicator Categories

4. Candle Patterns (60+)

Specify pattern name with optional trend (Bullish/Bearish). Compare against 0 to detect formation.

doji > 0                           // any doji
bullish engulfing > 0 15min
bearish doji > 0                   // bearish doji only
hammer > 0
morningstar > 0 4h

Popular Patterns

DOJI, HAMMER, ENGULFING, MORNINGSTAR, EVENINGSTAR, SHOOTINGSTAR, HANGINGMAN, HARAMI, HARAMICROSS, SPINNINGTOP, MARUBOZU, PIERCING, DARKCLOUDCOVER, 3WHITESOLDIERS, 3BLACKCROWS, ABANDONEDBABY, INVERTEDHAMMER, DRAGONFLYDOJI, GRAVESTONEDOJI, HIKKAKE, KICKING, BELTHOLD, COUNTERATTACK, ...

5. Price & Market Data

Price Aliases (OHLC Bar)

Quotes

Heikin Ashi

Close > AdaptiveCentricMa(200).value  // price above native smoother
bid > 1.1000                        // bid price check
spread > 5                           // spread filter
ha_close > ha_open                    // Heikin Ashi bullish bar
TrueRangePercentile.percentile > 80       // range/volatility pressure

6. Price Patterns (40)

Chart patterns detected automatically. Compare against 0 to detect formation.

DoubleBottom > 0
HeadAndShoulders > 0
BullFlag > 0
AscendingTriangle > 0 1h

DoubleBottom, DoubleTop, TripleBottom, TripleTop, HeadAndShoulders, InverseHeadAndShoulders, AscendingTriangle, DescendingTriangle, SymmetricalTriangle, BullFlag, BearFlag, BullPennant, BearPennant, RisingWedge, FallingWedge, CupAndHandle, DiamondTop, DiamondBottom, VBottom, WBottom, MTop, GapUp, GapDown, ...

Pattern Fields

OnFormationDone — the only field: a true/false flag that fires when the pattern completes. Compare against 0 (e.g. DoubleBottom > 0).

7. Trend, Channel, Price Move, Fibonacci, Pivot

Trend Object

trendside == 1                       // uptrend active
trendside == -1                      // downtrend active
fastprice > slowprice                  // fast EMA above slow

Price Move

A price move is a directional move measured from where it started: its width in ticks, its speed in ticks per second, and how long it has been running. Use this when you mean "price travelled N ticks" — not when you mean "N quote updates arrived".

price moves 100 ticks up within 120 sec   // ✔ prefills value=100, dir=Up, limit=120s
price move down 25 ticks                    // ✔ distance-only (no time limit)
price moved up 15 ticks in 3 seconds          // ✔ same shape, other wording
move_size > 50                             // ✘ no width/direction/source — Save fails

Three ways to express the same rule — pick by resolution

A · Tick source (recommended for seconds-scale rules). Quotes.MidPrice updates on every quote and takes no timeframe:

[
  { "ExpressionName": "SRC_MID",                     // tick-resolution getter
    "Expression_left_ElementType": "Quotes",
    "Expression_left_ElementValue": "MidPrice" },      // no Frame — Quotes is not frame-required

  { "ExpressionName": "PM_UP_100_IN_120S",
    "Expression_left_ElementType": "UserExpression",
    "Expression_left_ElementValue": "SRC_MID",
    "Expression_left_FieldName": "onPriceMove",
    "Expression_left_PriceMoveValue": 100,
    "Expression_left_PriceMoveDirection": "Up",
    "Expression_left_TimeLimitSeconds": 120 }
]

B · Bar source. Same shape, but the getter is a bar field and needs a Frame. Detection can only advance once per bar, so keep the frame well below the time limit:

[
  { "ExpressionName": "SRC_CLOSE_1Min",             // bar-resolution getter
    "Expression_left_ElementType": "OHLC_Bar",
    "Expression_left_ElementValue": "CLOSE_PRICE",
    "Expression_left_Frame": "1Min" },            // 5Min here would blind a 120s rule

  { "ExpressionName": "PM_UP_100_IN_120S_BAR",
    "Expression_left_ElementType": "UserExpression",
    "Expression_left_ElementValue": "SRC_CLOSE_1Min",
    "Expression_left_FieldName": "onPriceMove",
    "Expression_left_PriceMoveValue": 100,
    "Expression_left_PriceMoveDirection": "Up",
    "Expression_left_TimeLimitSeconds": 120 }
]

C · Quick Create (NLP). The phrase form prefills width, direction and time limit — you then pick the source getter in the builder and Save:

price moves 100 ticks up within 120 sec   // -> value=100, dir=Up, limit=120s
price move down 25 ticks                    // -> distance only, no time limit

How a price move is actually built

So "price moved 100 ticks up within 2 minutes" is one expression, not a comparison:

{
  "ExpressionName": "PM_UP_100_IN_120S",
  "Expression_left_ElementType": "PriceMoveObject",
  "Expression_left_ElementValue": "SRC_OHLC_Close_5Min",   // source expression
  "Expression_left_Frame": "5Min",
  "Expression_left_PriceMoveValue": 100,              // the 100 ticks
  "Expression_left_PriceMoveDirection": "Up",
  "Expression_left_TimeLimitSeconds": 120             // the 2 minutes
}

Any price-move field also works in the generic form pricemove_<field> — e.g. pricemove_getcurrentwidth.

Channel Object

upperchannel > close                  // price below upper channel
close < lowerchannel                  // breakdown below channel

Pivot Points

pp > close                            // price below pivot
s1 < low                              // low broke support 1
close > r1                            // price above resistance 1

Account Object

balance >= 10000
openpnl < -500

Open Position

Every field of LastOpenPositionObject — the strategy's most recent open position — is reachable as last_pos_<field>.

Both profit fields are signed by side: positive means the position is winning, for a BID and an ASK alike — so one expression covers both directions. Percent is 0.2 for 0.2%.

The two profit getters also have short aliases: profit_percent / pos_profit_pct and profit_ticks / pos_profit_ticks.

profit_percent >= 0.2                      // take profit at +0.2%
profit_percent <= -0.2                     // stop at -0.2% — put BOTH in Close Bid and Close Ask
last_pos_currentprofitpercent > 0.5       // winner: up 0.5% of entry
last_pos_currentprofitpercent < -0.2      // loser: percent stop, same on every symbol
last_pos_currentprofitpercent >= 0.1      // give-back level (see warning below)
last_pos_currentprofitticks > 50          // same idea in ticks

Careful with a bare profit threshold. A position opens at ~0% profit, so last_pos_currentprofitpercent < 0.1 is already true at entry and would close it immediately. For "profit dropped below 0.10%", AND it with proof the position reached that level first — the peak (unary MAX) at or above 0.1. MIN cannot express this: it reports the worst point, never that profit had risen.

8. Date & Time

datetime > DateValue.2026-01-01       // current date/time after fixed date
time < 14:00                         // before 2 PM (intraday hour check)

9. Operators

// Input  —  (Trend_Up OR Reversal) AND RSI_Below_30
( exp.Trend_Up OR exp.Reversal ) AND exp.RSI_Below_30

// step1 (intermediate, auto-created on Save)
exp.Trend_Up OR exp.Reversal

// final (loaded for approval)
UserExpression.[step1] AND exp.RSI_Below_30

// Leg 1
RSI(14) < 30                  // save as RSI_Below_30

// Leg 2
balance > 100                 // save as Balance_GT_100

// Combiner
UserExpression.RSI_Below_30 AND UserExpression.Balance_GT_100

[
  {
    "ExpressionName": "RSI_Below_30",
    "Expression_left_ElementType": "GTSIndicators",
    "Expression_left_ElementValue": "RSI",
    "Expression_left_Frame": "5Min",
    "Expression_left_Size1": 14,
    "Expression_left_operation": "<",
    "Expression_right_ElementType": "FixedVal",
    "Expression_right_ElementValue": "30"
  },
  {
    "ExpressionName": "Balance_GT_100",
    "Expression_left_ElementType": "AccountObject",
    "Expression_left_ElementValue": "Balance",
    "Expression_left_operation": ">",
    "Expression_right_ElementType": "FixedVal",
    "Expression_right_ElementValue": "100"
  },
  {
    "ExpressionName": "RSI_Below_30_AND_Balance_GT_100",
    "Expression_left_ElementType": "UserExpression",
    "Expression_left_ElementValue": "RSI_Below_30",
    "Expression_left_operation": "AND",
    "Expression_right_ElementType": "UserExpression",
    "Expression_right_ElementValue": "Balance_GT_100"
  }
]

// Input
RSI(14) crossed 30

// Leg 1 — prev vs prev  (a[1] < b[1]; index is a no-op if b is a constant)
RSI(14)[1] < 30            // RSI_14_below_30_prev

// Leg 2 — now above  (a > b)
RSI(14) > 30               // RSI_14_above_30_now

// Combiner (loaded for approval)
UserExpression.RSI_14_below_30_prev AND UserExpression.RSI_14_above_30_now

10. Timeframes

Append the timeframe at the end, e.g. 15min. (Expressions carry no symbol on Trading — the symbol is set on the strategy.)

11. Dot-Notation Mode

For precise control, use structured TYPE.FIELD.PARAMS.FRAME syntax.

Arithmetic — what the engine accepts, and where

Expression_left_operation accepts all twelve of these values (they are exactly the operator buttons in the visual builder):

A concrete, real example — this is how the bundled EMA_DIFF_H1_ABS Community expression is built. Note operation is "-" and the result is a number, so it is a helper, not an alert:

{
  "ExpressionName": "EMA_DIFF_H1_ABS",
  "Expression_left_ElementType": "UserExpression",
  "Expression_left_ElementValue": "EMA_1H_50_GETTER_H1",
  "Expression_left_operation": "-",          // math operator — returns a value
  "Expression_left_applyABS": true,
  "Expression_right_ElementType": "UserExpression",
  "Expression_right_ElementValue": "EMA_1H_200_GETTER_H1"
}

Then a second expression turns that number into a condition — UserExpression.EMA_DIFF_H1_ABS > FixedVal.0.0002. That two-step shape is the answer to every "calculated condition".

// Regular indicators
GTSIndicators.RSI.14.5Min < FixedVal.30
GTSIndicators.MACD.12.26.9.15Min.Signal > FixedVal.0
OHLC_Bar.CLOSE_PRICE.Daily > GTSIndicators.SMA.30.Daily

// Extended indicators / subsystems
ExtendedIndicators.InertialRsi.14.5Min.signal > FixedVal.30
ExtendedIndicators.AdaptiveMacdR2.20.12.26.9.15Min.signal > FixedVal.0
ExtendedIndicators.QuantileVolatilityBands.100.2.1Hour.upper > OHLC_Bar.CLOSE_PRICE.1Hour

// Candle patterns
TA_CandlePatterns.DOJI.Bullish.5Min > FixedVal.0

// Price bars
OHLC_Bar.CLOSE_PRICE.Daily > ExtendedIndicators.AdaptiveCentricMa.200.Daily.value
HeikinAshiBar.CLOSE_PRICE.5Min > HeikinAshiBar.OPEN_PRICE.5Min

// Objects
TrendObject.TrendSide == FixedVal.1
ChannelObject.UpperChannel > OHLC_Bar.CLOSE_PRICE
PivotObject.S1.Daily > OHLC_Bar.MIN_PRICE.Daily

// Account & date
AccountObject.Balance >= FixedVal.10000
AccountObject.OpenPNL < FixedVal.-500
DateValue.2026-06-01 > DateValue.2026-01-01
HourValue.14:00 > DateValue.CurrentSysDateTime

// Price patterns
PricePattern.DoubleBottom.OnFormationDone > FixedVal.0

12. Complete Examples

Momentum Signals

InertialRsi(14).signal < 30                 // oversold-style momentum
InertialRsi(14).signal > 70                 // overbought-style momentum
AdaptiveMacdR2(20,12,26,9).signal > 0     // MACD-style signal positive
InertialStochastic(5,34,3,3).signal < 20   // stochastic-style oversold
BreakOfStructure(5,5).signal != 0         // structure event

Trend Following

Close > AdaptiveCentricMa(200).value daily // above native smoother
AdaptiveCentricMa(50).value > AdaptiveCentricMa(200).value // fast above slow
KalmanTrendFilter.trend > 0              // strong trend
trendside == 1                         // GTS uptrend active

Staged Unary + History

// Step 1 — helper getter: one RSI value from close
RSI_Close = RSI applied to Close, collection size 15, frame 5Min

// Step 2 — helper getter: one EMA value applied to the RSI output
EMA9_RSI_Close = EMA applied to UserExpression.RSI_Close, collection size 9

// Step 3 — compare current EMA(RSI) to previous EMA(RSI)
EMA9_RSI_Close > EMA9_RSI_Close[1]          // a > b

// Step 4 — compare previous EMA(RSI) to two-bars-back EMA(RSI)
EMA9_RSI_Close[1] > EMA9_RSI_Close[2]     // b > c

// Final expression — true only when the last 3 EMA(RSI) values are rising
UserExpression.EMA9_RSI_now_gt_prev AND UserExpression.EMA9_RSI_prev_gt_prev2

// Exact JSON shape for the same recipe
[
  {
    "ExpressionName": "RSI_Close",
    "Expression_left_ElementType": "OHLC_Bar",
    "Expression_left_ElementValue": "CLOSE_PRICE",
    "Expression_left_Frame": "5Min",
    "Expression_left_UseRSI": true,
    "Expression_left_collectionSize": 15,
    "Expression_left_numElement": 15
  },
  {
    "ExpressionName": "EMA9_RSI_Close",
    "Expression_left_ElementType": "UserExpression",
    "Expression_left_ElementValue": "RSI_Close",
    "Expression_left_UseEMA": true,
    "Expression_left_collectionSize": 9,
    "Expression_left_numElement": 9
  },
  {
    "ExpressionName": "EMA9_RSI_now_gt_prev",
    "Expression_left_ElementType": "UserExpression",
    "Expression_left_ElementValue": "EMA9_RSI_Close",
    "Expression_left_operation": ">",
    "Expression_right_ElementType": "UserExpression",
    "Expression_right_ElementValue": "EMA9_RSI_Close",
    "Expression_right_UseHistoryElem": true,
    "Expression_right_historyIndex": 1,
    "Expression_right_collectionSize": 2
  },
  {
    "ExpressionName": "EMA9_RSI_prev_gt_prev2",
    "Expression_left_ElementType": "UserExpression",
    "Expression_left_ElementValue": "EMA9_RSI_Close",
    "Expression_left_UseHistoryElem": true,
    "Expression_left_historyIndex": 1,
    "Expression_left_collectionSize": 2,
    "Expression_left_operation": ">",
    "Expression_right_ElementType": "UserExpression",
    "Expression_right_ElementValue": "EMA9_RSI_Close",
    "Expression_right_UseHistoryElem": true,
    "Expression_right_historyIndex": 2,
    "Expression_right_collectionSize": 3
  },
  {
    "ExpressionName": "EMA9_RSI_last3_rising",
    "Expression_left_ElementType": "UserExpression",
    "Expression_left_ElementValue": "EMA9_RSI_now_gt_prev",
    "Expression_left_operation": "AND",
    "Expression_right_ElementType": "UserExpression",
    "Expression_right_ElementValue": "EMA9_RSI_prev_gt_prev2"
  }
]

Volatility & Bands

Close > QuantileVolatilityBands(100,2).upper // above upper band
TrueRangePercentile.percentile > 80       // high range percentile
VolatilityStateMachine.state != 0         // volatility regime active

Pattern Detection

bullish engulfing > 0 4h  // candle pattern
DoubleBottom > 0                        // chart pattern
hammer > 0 1h              // hammer on hourly

Support & Resistance

close > r1                              // above resistance 1
s1 < low                                // broke support 1
close > upperchannel                    // channel breakout

Risk Management

balance >= 10000                       // min balance
openpnl < -500                         // max open loss
spread < 3                             // max spread filter

13. Unary Expressions

A unary expression is a single operand with no comparison — it fires on its own when the operand is truthy / non-zero. Just type the operand by itself (no operator, no right side):

bullish engulfing                  // candle pattern — fires on formation
doji 1h                 // pattern on a timeframe
UserExpression.My_Signal           // a saved expression, on its own
KalmanTrendFilter.trend            // fires when the value is non-zero

14. History (Previous Bars)

Append [N] to any operand to read it N bars back — the same notation the builder shows in dot-notation. [0] or no suffix = the current bar.

Close[1] > Close[2]                // previous close above the one before
RSI(14)[1] < 30                // RSI on the previous bar
direction[1] > 0               // previous bar closed up
high[1] > SMA(20)                  // prior high vs current SMA(20)