TradingView to Match-Trader — strategy alerts become signals

Risk warning: Trading CFDs and other leveraged products is complex and carries a high risk of losing money rapidly because of leverage. Industry data indicates that 70–80% of retail trading accounts lose money on these products. 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 for Telegram and Discord signals; a TradingView alert becomes a reviewable signal and, for placement, only an MT5 account can be assigned to it.

1. 1

   Create your PipSync account and subscribe to a plan

   Sign up at app.pipsync.io and subscribe to a plan that includes webhook integration (payment method required). It covers the webhook URL and the Recent alerts list.

2. 2

   Generate your TradingView webhook URL

   In the dashboard, go to Settings → Advanced → TradingView Alerts and click Generate webhook URL. PipSync generates a unique webhook URL containing a secret token and shows it only once. Treat it like a password — anyone who has it can send signals into your workspace — and regenerate it on the same screen if it is ever exposed.

3. 3

   Match-Trader for Telegram and Discord signals

   TradingView alerts cannot be placed on Match-Trader. For Telegram and Discord signals, open Trading Accounts → Add account and choose Match-Trader; start with a demo or evaluation account.

4. 4

   Know what the alert becomes

   Each valid alert becomes a signal on the Signals page for you to review. A lots value in the alert payload is ignored, and PipSync places no order from the alert by itself.

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 — instrument, direction, entry, sl and tp1, with real prices (not 0) for sl and tp1. 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

   Fire a test alert

   Fire the alert once, then open Settings → Advanced → TradingView Alerts and check Recent alerts: each call is listed with its status and, if rejected, the exact error. A valid alert shows up on the Signals page. Check a few alerts until they 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. For Telegram and Discord signals, orders reach Match-Trader through a direct REST and WebSocket integration running in the cloud; TradingView alerts are saved as signals only.

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 the instrument, a direction (buy or sell), an entry price, a stop-loss and a take-profit — all required, and a price of 0 is rejected. There is no close action.

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 and saves it as a signal on the Signals page; it does not place an order on Match-Trader, and TradingView alerts cannot be placed on Match-Trader.

Because you author the JSON yourself, there is little parsing ambiguity: what your strategy fires is what lands in the signal, and a malformed alert is rejected with a reason you can read under Recent alerts.

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; complying with your firm's rules remains your responsibility.

Prop accounts typically enforce daily and overall drawdown limits, and a lots value hardcoded into a TradingView alert would ignore your account balance and the stop distance of the specific trade.

That is why PipSync ignores it: for Telegram and Discord signals executed on Match-Trader, it computes the lot size server-side from your sizing settings. TradingView alerts are not placed on Match-Trader.

Whatever you do, 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, a TradingView alert gives you ownership of the entry logic but only produces a signal you review, while the Telegram route executes a feed someone else produces, with server-side sizing, min/max lots and max open positions. If your signals come from a Telegram channel rather than your own charts, the telegram-to-match-trader guide covers that route.