TradingView to Match-Trader — execute strategy alerts automatically

Risk warning: CFDs are complex instruments with a high risk of losing money rapidly due to leverage. 70–80% of retail investor accounts lose money when trading CFDs. Risk disclosure · Past performance.

The TradingView-bridge ecosystem grew up around MetaTrader, which leaves traders on Match-Trader — the backend a growing number of prop firms white-label — without a clean way to automate. PipSync connects to Match-Trader directly through its REST and WebSocket interfaces, so the same Pine Script strategy or indicator alert that fires into MT5 can fire into a Match-Trader evaluation or funded account, with percent-risk sizing and trade guardrails enforced before any order is sent.

1. 1

   Create a free PipSync account

   Sign up at app.pipsync.io — no credit card needed. The free plan covers everything this route requires for testing: a webhook source, a Match-Trader connection and server-side risk rules.

2. 2

   Add a TradingView webhook source

   In the dashboard, go to Sources → Add Source → TradingView Webhook. PipSync generates a unique webhook URL containing a secret token. Treat it like a password — anyone who has it can send signals to your account — and regenerate it from the Sources page if it is ever exposed.

3. 3

   Connect your Match-Trader account

   Add a broker account and choose Match-Trader. Connect the evaluation, funded or demo account you want trades executed on — starting with a demo or evaluation account is strongly recommended.

4. 4

   Set risk rules before the first alert fires

   Choose percent-risk sizing if your account has drawdown limits, and add guardrails such as max open trades and symbol filters. Note that a lots value hardcoded in the alert payload overrides these rules — omit the lots field if you want PipSync to size positions for you.

5. 5

   Create the TradingView alert

   In TradingView (a paid plan is required for webhook notifications), open the Alerts panel, set your condition, and paste the JSON template into the message field — placeholders like {{ticker}}, {{close}} and {{strategy.order.action}} fill in the symbol, price and direction at fire time. Then paste your PipSync URL under Notifications → Webhook URL and save.

6. 6

   Send a test signal

   In PipSync, open your TradingView source and use Send Test Signal. It posts a sample payload and shows you the parsed result and whether Match-Trader accepted the order. Keep Manual Approval mode on until live alerts behave exactly as expected.

Typical setup time: about 12 minutes.

Because most TradingView-to-broker bridges were built around MetaTrader: they forward the webhook into an Expert Advisor running inside an MT4/MT5 terminal, so any platform that cannot run MQL EAs never made their list. Match-Trader has no EA mechanism, so it stayed unsupported even as prop firms adopted it as a white-label backend.

PipSync does not depend on a terminal-side component at all. Orders reach Match-Trader through a direct REST and WebSocket integration running in the cloud, sitting alongside PipSync's other live destinations: MT4, MT5, cTrader, Binance Futures and Bybit. That also means you can re-point an existing strategy from an MT5 account to a Match-Trader account without rewriting a single alert.

The alert's message field carries a small JSON payload, and TradingView POSTs it to your unique PipSync webhook URL the moment the alert fires. The payload names an action (buy, sell or close), the symbol as your Match-Trader account lists it, and optionally an entry price, stop-loss, take-profit and lot size — a price of 0 means execute at market, and close flattens the open position on that symbol.

TradingView placeholders make the payload dynamic: {{ticker}} fills in the chart symbol, {{close}} the price at trigger time, and {{strategy.order.action}} the direction your Pine Script strategy decided. PipSync validates the payload, applies your server-side risk rules and submits the order to Match-Trader.

Because you author the JSON yourself, there is no interpretation step and no parsing ambiguity: what your strategy fires is exactly what gets executed, after your risk rules have had the final say.

It depends entirely on the firm, and you must verify before going live. Prop firms differ widely on automation: some permit personal automated strategies, some restrict third-party copy trading, some require pre-approval for any EA-style execution, and the rules can differ between evaluation and funded stages — or change over time.

A TradingView strategy you built yourself is your own trading logic rather than a copied third-party feed, which is how many firms frame the distinction. But the only answer that counts is the one in your firm's current terms or from its support team. PipSync executes what you configure; staying inside your firm's rules remains your responsibility.

Prop accounts typically enforce daily and overall drawdown limits, and a fixed lots value hardcoded into a TradingView alert ignores both your current equity and the stop distance of the specific trade — the same alert can therefore put very different amounts at risk from one fire to the next.

With percent-risk sizing, PipSync computes the lot size server-side from your chosen risk percentage and the stop-loss in the payload, so position size stays proportional instead of static. Combined with max-open-trades caps and symbol filters, this keeps your exposure rule-shaped rather than alert-shaped.

One detail matters: a lots field in the payload overrides your configured sizing for that trade. If you want PipSync to size positions, leave lots out of the alert message entirely. And whatever sizing you choose, you remain responsible for monitoring the account against your firm's specific limits.

The destination is the same; the source could hardly be more different. A TradingView alert is structured JSON generated by your own indicators or Pine Script strategy — deterministic, instant, and fired by TradingView's servers whenever the chart condition is met. A Telegram signal is a human-written message from a third-party provider, which PipSync has to parse with AI because every provider formats differently.

Practically, that means the TradingView route gives you full ownership of the entry logic and zero dependence on a signal provider, while the Telegram route automates a feed someone else produces. The server-side risk layer — sizing, guardrails, manual approval — works identically on both. If your signals come from a Telegram channel rather than your own charts, the telegram-to-match-trader guide covers that route.