Skip to content

Choosing a preset#

In step 0 of the strategy wizard, the Choose your indicator screen lists every active built-in preset plus the always-available I'll configure it myself option.

What each preset gives you#

Bundled with the preset What it does
Payload mapping Translation rules from the indicator's raw payload to v2. Copied onto the webhook on apply.
Default strategy TP levels, action lists, sizing. Loaded into step 2 — you can edit.
Settings Things like qty_mode, tp_source. Merged onto the webhook.
Alert message template The exact JSON to paste into TradingView (or "no copy-paste needed" for Pine alert() presets).
Paste destination TradingView Message box, indicator settings panel, or Pine alert().

TradingView paste destinations#

Indicators expose alerts in one of three ways. The wizard shows you the right place for the JSON.

Pine alert() — no copy-paste#

The indicator emits JSON itself via Pine's alert() calls. Best UX.

  • TradingView alert condition: Any alert() function call.
  • TradingView Message box: empty.

Used by the Signal Connector.

TradingView alert dialog → Message box#

Classic alertCondition() indicators. Each named alert needs its own JSON pasted into the alert dialog's Message box.

  • TradingView alert condition: the specific named alert.
  • TradingView Message box: the rule's JSON from the TradingView JSON tab on step 3.

You'll create one TradingView alert per HookTrader rule (entry, tp1, tp2, sl, …).

Indicator's own settings panel#

Some indicators (e.g. LuxAlgo Signals & Oscillators) take JSON inside their own settings panel via "Any alert() function call settings". Paste each rule's JSON into the matching field, then create one TradingView alert with condition Any alert() function call.

On apply#

When you pick a preset and continue:

  • Step 1 — name + exchange.
  • Step 2 — strategy is pre-filled from the preset. Review TP actions, sizing, slippage handling.
  • Step 3 — capture-and-map is pre-populated with the preset's rules. Fire a test alert; existing captures should immediately map cleanly.
  • Step 4 — review and activate.

If a real alert fails to validate against the preset's mapping, either the indicator's payload has changed since we authored the preset, or you've got a different version of the indicator on chart. Open Edit mapping and adjust by hand.

Deactivated presets#

Old / replaced presets are deactivated rather than deleted — they're hidden from the picker but the row survives so any webhook that previously applied them still shows the historical context.

See also#