TradingView to Binance — alerts become signals you review

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.

A TradingView alert can send a webhook but cannot hold exchange API keys or place orders by itself. PipSync sits in between: it receives the alert, validates it and saves it as a signal you review; Binance Futures accounts connect only for Telegram and Discord signals. Crypto markets never close, and neither does the pipeline — there is no script on a rented server that can crash on a Saturday night.

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, cancel any time). It covers generating the webhook URL and checking Recent alerts.

2. 2

   Get your PipSync webhook URL

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

3. 3

   Binance Futures for Telegram and Discord signals

   TradingView alerts cannot be placed on Binance. If you also want Telegram or Discord signals executed on Binance Futures, create a dedicated trade-only API key (withdrawals disabled) and add it under Trading Accounts → Add account.

4. 4

   Create the TradingView alert

   In TradingView (a paid plan is required for webhook alerts), set your alert condition, paste the JSON payload (instrument, direction, entry, sl, tp1 — with real prices for sl and tp1) into the Message field — using placeholders like {{strategy.order.action}}, {{ticker}} and {{close}} — and paste your PipSync URL under Notifications → Webhook URL.

5. 5

   Know what the alert becomes

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

6. 6

   Fire a test alert and verify

   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 appears on the Signals page. Test with a few alerts first.

Typical setup time: about 12 minutes.

Not on their own. A TradingView alert can fire a webhook — an HTTP POST with a message you define — but it cannot store exchange API keys, size a position or submit an order. PipSync supplies the missing layer: the alert posts JSON to your private PipSync webhook URL, PipSync validates it and saves it as a signal for you to review — it does not place the order, and alerts cannot be placed on Binance.

There is nothing to deploy, patch or keep alive: PipSync's webhook runs server-side around the clock, so alerts that fire at night still arrive as signals. Placing them on Binance Futures is not available yet; Telegram and Discord signals can be executed there.

PipSync expects a small JSON object in the alert's Message field. TradingView fills in the dynamic parts through placeholders: {{strategy.order.action}} becomes buy or sell when a strategy order fires, {{ticker}} becomes the chart's symbol, and {{close}} the current price.

One crypto-specific quirk: on Binance perpetual charts, {{ticker}} resolves with a ".P" suffix (for example BTCUSDT.P), while the exchange instrument is plain BTCUSDT. Fire a test alert and check how the instrument was read under Recent alerts in the PipSync dashboard — or hard-code the literal instrument name in the message if you prefer zero ambiguity. The exchange rejects symbols it does not recognize, so a mismatch fails visibly rather than trading the wrong contract.

• instrument — the chart symbol or the exchange name, e.g. BTCUSDT (crypto spellings such as BTCUSD or XBTUSD are normalised to BTCUSDT)
• direction — buy or sell (long and short also work); there is no close action
• entry — entry price, above 0 (0 is rejected, not read as market)
• sl — stop-loss price, above 0
• tp1 — at least one take-profit price, above 0
• everything else, including lots and comment — ignored

An alert never sets a size: a quantity field in the payload is ignored and no order is placed from the alert. Sizing settings apply to Telegram and Discord signals executed on Binance Futures.

Remember that leverage and margin mode are settings on your exchange account, separate from order quantity. Review those exchange-side settings before trading Telegram or Discord signals there — PipSync does not set leverage.

No. An alert becomes a signal for review; PipSync places no order from it by itself, so there is nothing to close. For Telegram and Discord signals executed on Binance Futures, PipSync supports the reduce-only flag, which the exchange rejects if the position is already flat.

TradingView alerts cannot send a close action — a direction other than buy or sell is rejected — so exits stay with you on Binance.

If you add a Binance account for Telegram or Discord signals, create a dedicated API key just for PipSync with futures trading only. Leave withdrawals disabled — a key without withdrawal rights limits the damage if anything ever leaks. You can revoke the key on Binance at any moment, which cuts PipSync's access instantly without touching your account.

The same discipline applies to the webhook URL: it contains a secret token, so anyone holding it can send signals into your workspace. Keep it out of public Pine scripts and shared screenshots, and regenerate it under Settings → Advanced → TradingView Alerts if you suspect exposure.