TradingView to cTrader — turn webhook alerts into orders

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.

cTrader has no native way to receive TradingView alerts, and most webhook bridges were built for MetaTrader. PipSync closes that gap for ECN/STP traders: your strategy fires the alert, PipSync validates it against your server-side risk rules — sizing, SL/TP, max open trades, symbol filters — and submits the order via the Open API. It works on demo and live accounts, and demo-first testing is built into the workflow.

1. 1

   Create a free PipSync account

   Sign up at app.pipsync.io — no credit card required. You only need the dashboard to generate the webhook URL your TradingView alert will call, and the free plan covers building and testing this route.

2. 2

   Connect your cTrader account

   Add a broker account and choose cTrader. You authorize PipSync through your cTrader ID using Spotware's official Open API and pick the trading account the route executes on — start with a demo account.

3. 3

   Get your PipSync webhook URL

   Go to Sources → Add Source → TradingView Webhook. PipSync generates a unique URL containing a secret token. Copy it and keep it private — this URL is the credential TradingView will use to reach your account.

4. 4

   Create the alert in TradingView

   Open the Alerts panel (Alt+A), set your strategy or price condition, and paste PipSync's JSON template into the Message field — action and symbol are required; SL, TP and lots are optional. Then paste your webhook URL under Notifications → Webhook URL and save. Note that webhook notifications need a paid TradingView plan.

5. 5

   Check the symbol mapping

   Make sure the payload's symbol matches your cTrader broker's instrument name exactly. If your chart's {{ticker}} placeholder resolves to something different from the broker's naming, write the broker symbol into the alert message directly.

6. 6

   Test on demo, then go live

   Use Send Test Signal in the dashboard to fire a sample payload and confirm the broker accepts the order. Let a few real alerts run on the demo account — with Manual Approval on if you want to confirm each trade — before switching the route to your live account.

Typical setup time: about 12 minutes.

Not on their own. TradingView can fire a webhook alert — an HTTP POST carrying a JSON message — but cTrader has no built-in way to receive webhooks, so out of the box an alert is just a notification.

The traditional workaround is installing a cBot or a third-party bridge inside the cTrader terminal and keeping that terminal running around the clock. PipSync removes the terminal from the loop entirely: its cloud endpoint receives the webhook, applies your risk rules, and submits the order to your account through Spotware's official Open API. Nothing runs on your machine.

PipSync expects a small JSON payload in the alert's Message field. The minimum is an action and a symbol; everything else is optional and falls back to your configured risk rules.

When creating the alert, paste your unique PipSync webhook URL under Notifications → Webhook URL. Treat that URL like a password — anyone who has it can post signals to your route — and regenerate it from the Sources page if it is ever exposed.

• action (required): "buy", "sell" or "close" — strategy alerts can use the {{strategy.order.action}} placeholder for entries
• symbol (required): the instrument name exactly as your cTrader broker lists it
• price (optional): an entry price; 0 means execute at market
• sl / tp (optional): stop-loss and take-profit price levels; 0 to omit
• lots (optional): overrides your configured risk sizing for that one trade

Use the symbol name from your cTrader watchlist, not TradingView's chart ticker. TradingView identifies instruments by data feed — a chart might show OANDA:XAUUSD — while your cTrader broker may use its own naming or suffixes for the same market.

PipSync's payload takes the symbol exactly as it appears in your broker's symbol list. The {{ticker}} placeholder works when your chart's ticker happens to match the broker's name; when it does not, type the broker symbol directly into the alert's JSON. Since alerts are created per chart, this is a one-time decision per instrument.

The quickest way to verify a mapping is the built-in test signal: it shows you the parsed payload and whether your broker accepted the order, before any live alert ever fires.

Because nothing has to stay running on your side. A cBot only executes while the cTrader terminal is open, which in practice means renting a Windows VPS and maintaining the bot through platform updates. PipSync's route is server-to-server: TradingView posts to PipSync's cloud, and PipSync talks to Spotware's Open API.

It also keeps your risk layer in one place. Server-side sizing, SL/TP handling, max open trades and symbol filters apply to this route exactly as they do to PipSync's other routes — whether the signal came from a TradingView alert or a Telegram channel, the same guardrails run before any order reaches your broker.

Demo first, always. Connect a cTrader demo account, point the route at it, and use Send Test Signal in the PipSync dashboard to fire a sample payload — you immediately see how it parsed and whether the broker accepted the resulting order.

Then let real alerts run on demo. Enable Manual Approval mode so each incoming alert waits for your confirmation, check that direction, symbol, SL/TP and size come out the way your strategy intended, and only then switch the route to the account you actually want to trade.