How to Automate TradingView with TradersPost

TradingView plots signals — it doesn't place orders. TradersPost is the bridge that turns a Pine Script alert into a real fill at your prop firm's broker. Here's the full setup.

Published 2026-04-26

TradingView is a charting and alerting platform — on its own, it can't touch your broker account. TradersPost fills that gap: it listens for a TradingView webhook alert, translates it into a broker order, and routes it to Tradovate, Rithmic, NinjaTrader, MT4/MT5, or Alpaca. Below is the full setup, plus the JSON alert format a Pine Script strategy needs to emit.

Step 1: Create a TradersPost account

Sign up at traderspost.io. Their entry-level paid plan covers one broker connection and unlimited strategies — enough for a single prop firm evaluation. Check the current plans on their pricing page, since tiers and promotions change.

Step 2: Connect your prop firm's broker

Under Brokers → New, add the connection that matches your prop firm:

Apex / Topstep / MyFundedFutures — Tradovate or Rithmic
FTMO — MetaTrader 5 or cTrader
Forex-focused funded programs — MetaTrader 5

Tradovate connects through an OAuth flow; Rithmic uses a login and password. Either way the connection is read/write — TradersPost can place orders, see fills, and read account state.

Step 3: Create a strategy in TradersPost

Under Strategy → New, map the strategy to:

Symbol — e.g. MNQ for Tradovate, or the equivalent CFD symbol for MT5
Quantity — contracts per signal
Bracket / OCO — turn this on so a stop and target fire as a single linked order group

TradersPost generates a unique webhook URL for the strategy in the form https://webhooks.traderspost.io/trading/webhook/<uuid>/<token>. Save it.

Step 4: Wire the alert in TradingView

Add the Pine Script to a chart, then right-click → Add Alert. In the alert dialog:

Set Condition to the strategy, firing on "Order fills only" rather than "Once per bar close"
Paste the TradersPost webhook URL into the Webhook URL field
Set the Message body to the strategy's JSON payload

The JSON payload

TradersPost expects a specific alert message shape. A typical Pine Script strategy alert looks like this:

JSON

{
  "ticker": "{{ticker}}",
  "action": "{{strategy.order.action}}",
  "quantity": {{strategy.position_size}},
  "price": {{close}},
  "sentiment": "{{strategy.market_position}}"
}

Every strategy sold through our store ships with this alert message pre-filled in the script's input panel — copy it directly into the TradingView alert dialog.

Step 5: Paper-test before connecting a live evaluation

TradersPost includes a paper-trading environment. Run the strategy there for at least 5 sessions and confirm:

Entries fire near the price the script signaled, within reasonable slippage
Stops and targets are placed correctly as a bracket order
No duplicate orders fire from a single bar

Duplicate entries almost always trace back to the TradingView alert being set to "Once per bar" instead of "Order fills only." Switching the fire-on condition usually resolves it.

Step 6: Connect to the live evaluation account

Once paper trading looks clean, point the strategy's broker target at the live evaluation account inside TradersPost. Start with the smallest viable contract size on day one and watch the first several fills manually before leaving it unattended.

Common gotchas

Symbol mismatch. TradingView's continuous contract symbol (e.g. MNQ1!) isn't the same string your broker expects (e.g. a specific front-month code) — TradersPost handles the mapping, but double-check the strategy's symbol field after every rollover.
Time zone. A Pine Script session filter and the broker connection both need to agree on the same time zone — America/New_York is standard for US futures.
TradingView plan tier. Webhook alerts require a paid TradingView plan; the free tier can't fire them.