JSON alert templates for TradersPost & PineConnector

When you automate a strategy, the TradingView alert is the instruction the bridge executes. Structured, with dynamic placeholders, so each entry and exit carries the right action and size. (Generate one fast with the Pine alert generator.)

Pine placeholders you'll use

Inside a strategy() script, alert messages can include order-aware variables:

{{ticker}}                    // symbol
{{strategy.order.action}}     // buy / sell
{{strategy.order.contracts}}  // quantity
{{strategy.order.price}}      // fill price

TradersPost (futures → Tradovate / TopstepX)

TradersPost expects JSON. A representative entry payload:

{
  "ticker": "{{ticker}}",
  "action": "{{strategy.order.action}}",
  "quantity": "{{strategy.order.contracts}}",
  "price": "{{strategy.order.price}}"
}

Exits typically send an action of exit or a flat/close signal. Exact accepted fields evolve — confirm against docs.traderspost.io.

PineConnector (MT5 → NAS/XAU)

PineConnector reads a comma-separated message line, not JSON. The shape is licence id, command, symbol and risk parameters:

LICENCE_ID,buy,NAS100,risk=1
LICENCE_ID,closelong,NAS100

Use your real licence id and the exact command keywords from docs.pineconnector.com.

Is the PineConnector message a webhook?

Yes — the delivery mechanism is a standard TradingView webhook alert. What differs is the body: TradersPost parses JSON fields, PineConnector parses the comma-separated line above. In both cases TradingView fires the alert, sends the body to the bridge's webhook URL, and the bridge places the order — which is why both need a TradingView plan with webhook alerts enabled, and why the alert message, not the script, is what the bridge actually sees. Costs of both bridges are broken down in TradersPost vs PineConnector.

Common mistakes

• Symbol mismatch — the alert ticker must map to the broker symbol the bridge expects.
• Missing exit alerts — entries automate but positions never close.
• Wrong script type — order placeholders need a strategy(), not an indicator. See strategy vs indicator alerts.
• Static quantity — hardcoding size instead of {{strategy.order.contracts}} breaks multi-contract sizing.

Once the alert is right, see how to automate MNQ end-to-end and the setup guide.

FAQ

Does TradingView send JSON to TradersPost?

Yes — TradersPost parses a JSON alert body containing the ticker, action, quantity and optional price, populated by Pine placeholders like {{strategy.order.action}}.

What format does PineConnector use?

A comma-separated message line (licence id, command, symbol, risk), not JSON — delivered through a standard TradingView webhook alert. Use the exact command keywords from PineConnector's documentation.

Why isn't my automated strategy closing positions?

You likely only set entry alerts. Add exit alerts (an exit/close action) so the bridge flattens the position.

Do I need a strategy() or an indicator for alerts?

For order-aware alerts that carry action and quantity, use a strategy(). Indicator alerts can fire but don't include order placeholders, so they need manual mapping.

Not financial advice. Performance figures referenced are hypothetical, modeled outputs (1,500-path Monte Carlo on a backtest + live sample). Past performance does not guarantee future results. Tool names are referenced for education; verify current features and prop-firm rules directly.