Guide

Alerts & automation

TheStrat Suite, a free open-source TheStrat indicator for TradingView, sends an alert when a Strat setup goes in force on any of six timeframes, by push, email or webhook. The webhook can feed a broker bridge or your own code. This page covers every alert condition, what the message contains, a webhook payload you can copy, and what the Suite does not do.

The two kinds of alert

1. The consolidated alert (the rich one)

Create one TradingView alert on the indicator with the condition Any alert() function call. On each bar it checks every enabled timeframe for a signal that just went in force and sends one message for all of them:

1H 2d-1-2u HAM 🟢 | @ 542.10 MAG 545.30 EXH 548.20 STOP 538.10 | FTFC Up

• 1H 2d-1-2u HAM: the timeframe, the combo, and HAM/SHO if C1 was a hammer or shooter.
• 🟢 bull, 🔴 bear.
• @ trigger, MAG magnitude target, EXH exhaustion, STOP stop. Each is opt-in under Alerts - Detailed and left out when it does not exist for that signal.
• FTFC Up / FTFC Down / Conflict: appended when Include FTFC is on.
• Several events on one bar join with | , as below.

15m F2d-2u 🟢 | 1H 2d-1-2u 🟢 | FTFC Up

Per-timeframe checkboxes decide which timeframes feed this alert. Dominoes join the stream only if Include in Consolidated Alerts is on, as Domino: 15m+30m+1H.

2. Named alert conditions (for routing)

These appear in TradingView's Condition dropdown:

The indicator gives these a fixed default message. You write the actual message in TradingView's alert dialog, and it can use TradingView placeholders such as {{ticker}}, {{close}}, {{interval}} and {{timenow}}. That is how you get JSON out for a bridge.

Delivery: push, email, webhook

All of this is TradingView's own alert delivery: app push, email, and webhook URL (webhooks need a paid TradingView plan). Set the chart timeframe at or below the smallest timeframe the Suite monitors, because TradingView cannot read timeframes lower than the chart.

A webhook payload example

Most broker bridges (TradersPost, PineConnector, 3Commas and others) and most custom receivers expect JSON. The consolidated alert's message is plain text, so for a bridge use a named condition and write the JSON yourself. For example, on Signal In-Force (Bullish):

{
  "ticker": "{{ticker}}",
  "action": "buy",
  "price": "{{close}}",
  "interval": "{{interval}}",
  "time": "{{timenow}}",
  "source": "TheStrat Suite: Signal In-Force (Bullish)"
}

Make a second alert on Signal In-Force (Bearish) with "action": "sell". Field names differ by bridge, so copy the exact schema from your bridge's docs. If you want the combo, targets and stop in your own code, send the consolidated alert to your webhook instead and parse the text: split on | , read the timeframe and combo from the first token, and the prices after @, MAG, EXH and STOP.

Passing it to a broker bridge

1. Configure the Suite: timeframes, the signal families you trade, and filters such as FTFC or Lead Signal. Alerts follow the same toggles as the chart.
2. Create the bridge's strategy or webhook endpoint and copy its URL and JSON format.
3. In TradingView, create the alert on TheStrat Suite, pick the condition, paste the JSON into Message and the URL into Webhook URL.
4. Test on paper or a simulated account first. Watch a few alerts arrive before any real money is involved.
5. After you update the indicator, delete and recreate the alerts. TradingView alerts stay bound to the script version they were made with.

What it does not do

• It does not place orders. The Suite is an indicator. It finds setups and sends alerts; a bridge or your own code places the trade.
• It does not size positions or manage exits. The stop and targets in the message are levels for you or your code to use. Nothing trails or closes a position for you.
• Named conditions carry no prices. Only the consolidated alert carries the trigger, targets and stop, and it is plain text, not JSON.
• Alerts are per family, not per exact combo. To trade only 3-1-2s, filter on the message text in your receiver.
• It is not a backtest. There is no strategy version and no performance report. Test before you automate.
• Previews stay quiet. A timeframe that is previewing next period's levels (market closed) or showing ? in the table never fires alerts.

Every alert setting is documented in the Settings Reference; how the message is built is in Reading the Chart. The combos themselves are listed in Strat combos.

Trading involves risk of financial loss. Automated trading adds its own: missed or duplicated webhooks, bridge outages, slippage. This is a charting tool, not financial advice.