Skip to main content
Home›Integrations›TradingView → Binance
TradingView → Binance Futures · setup guide

TradingView to Binance — alerts become signals you review

To connect TradingView to Binance Futures, point your alert's webhook at PipSync: when your Pine strategy or indicator fires, TradingView POSTs a JSON payload to your private PipSync URL, and PipSync validates it server-side and saves it as a signal on the Signals page for you to review — 24/7, with no bot to host. By default PipSync places no order from an alert, and Binance Futures accounts are gateway-connected, so for now the risk of a crypto trade cannot be measured on them: an alert is not auto-traded there; it is only recorded as a signal and cannot be placed there from PipSync for now. Telegram and Discord signals still execute on Binance Futures.

Billed at checkout · Cancel any time · Free plan available

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. PipSync sits in between: it receives the alert, validates it and saves it as a signal you review. Auto-trade from TradingView is opt-in and off by default; on Binance Futures accounts an alert is not auto-traded for now, while Telegram and Discord signals still execute there. Crypto markets never close, and neither does the pipeline — there is no script on a rented server that can crash on a Saturday night.

TradingView → Binance Futures at a glance

Signal sourceTradingView alerts (strategy or indicator) via webhook — requires a paid TradingView plan
DestinationTelegram and Discord signals execute on Binance Futures; a TradingView alert is not auto-traded there for now; it is only recorded as a signal and cannot be placed there from PipSync for now
Webhook endpointA unique per-workspace URL (https://pipsync.io/api/tradingview/webhook/<your-token>) — keep it secret
Alert payloadJSON: instrument, direction (buy / sell), entry, sl and tp1 — all required, sl/tp above 0
Order controlsSizing and limits apply to Telegram and Discord signals; an alert that names its own size is recorded as a signal
Auto-tradeOpt-in and off by default (Advanced plan); on Binance Futures accounts the risk of a crypto trade cannot be measured for now, so an alert is not auto-traded there
InfrastructureFully cloud-based — no VPS, no self-hosted bot, runs while your computer is off
PriceWebhook integration needs a plan that includes it (the Advanced plan)

How do I connect TradingView to Binance Futures?

One half of the setup lives in the PipSync dashboard, the other in TradingView's alert dialog. Nothing is installed on your machine.

  1. Create your PipSync account and subscribe to a plan

    Sign up at app.pipsync.io (the $0 Free plan needs no card but only parses signals), then 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. 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, once auto-trade is on, trigger trades. Regenerate it on the same screen if you suspect a leak.

  3. Binance Futures for Telegram and Discord signals

    TradingView alerts are not auto-traded on Binance for now: the risk of a crypto trade cannot be measured on gateway-connected accounts. 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. 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. Leave size fields such as lots or qty out of the message: an alert that names its own size is recorded as a signal.

  5. Know what the alert becomes

    Each valid alert becomes a signal on the Signals page for you to review, and by default PipSync places no order from it. Only JSON alerts can auto-trade; a plain-text alert is always recorded as a signal, and so is an alert that names its own size (for example lots, qty, contracts, size, volume, units, amount or risk).

  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.

  7. Optional: switch on auto-trade

    Auto-trade is opt-in and off by default, and it needs the Advanced plan: under Settings → Advanced → TradingView Alerts you give an explicit consent and click Set up auto-trading, then link your accounts and switch auto-trade on under Accounts & auto-trade. Until you do, every alert stays a recorded signal — and on Binance Futures accounts an alert is not auto-traded for now.

Typical setup time: about 12 minutes.

Can TradingView alerts trade on Binance Futures directly?

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, and PipSync validates it and saves it as a signal for you to review. By default it places no order from the alert, and Binance Futures accounts are gateway-connected, so for now the risk of a crypto trade cannot be measured on them: an alert is not auto-traded there; it is only recorded as a signal and cannot be placed there from PipSync for now.

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. Telegram and Discord signals still execute on Binance Futures.

Can TradingView alerts place trades on Binance automatically?

Not on Binance Futures for now. Auto-trade is opt-in and off by default. It needs the Advanced plan: you set it up under Settings → Advanced → TradingView Alerts with an explicit consent (Set up auto-trading), then link your accounts and switch auto-trade on under Accounts & auto-trade. Binance Futures accounts are gateway-connected, so for now the risk of a crypto trade cannot be measured on them: an alert is not auto-traded there; it is only recorded as a signal and cannot be placed there from PipSync for now. Telegram and Discord signals still execute there. The signal is only recorded on the Signals page: a TradingView signal cannot be placed on Binance from there either.

With auto-trade on, the loss at the stop loss is capped at the channel risk, 0.5% of the account balance by default. If the risk cannot be measured on an account (the balance is unknown, there is no contract data, or the account is not held in USD for now — for now, auto-trade values the risk only for currency pairs: gold, indices, crypto and other CFDs on MT5, cTrader and Match-Trader accounts are not traded), or the broker's smallest lot would exceed the cap, that account is not traded. If every account was refused by these limits, the alert is only recorded as a signal and cannot be placed there from PipSync for now; if the broker rejects the order on every account, the signal is marked rejected. Slippage and price gaps can make the actual loss larger than the cap. If the de-duplication service is unavailable, alerts are only saved as signals. An alert is traded automatically only when all of these hold:

  • it is a JSON alert — plain-text alerts are always recorded as a signal
  • it comes from TradingView's published sender IP addresses
  • it names no size of its own (for example lots, qty, contracts, size, volume, units, amount or risk) — otherwise it is a recorded signal
  • your Advanced plan is still active
  • it is not a duplicate — TradingView retries are de-duplicated
  • your workspace is under 5 automatic executions per minute
  • no position in the same instrument opened by a TradingView alert is still open, in either direction

What should the alert payload look like for Binance symbols?

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. Only JSON alerts can auto-trade; a plain-text alert is always recorded as a signal.

  • 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
  • comment — ignored
  • lots, qty, contracts, size, volume, units, amount or risk — never used for sizing; an alert carrying one is recorded as a signal

Does the alert set a position size?

An alert never sets a size: an alert that names its own size (for example lots, qty, contracts, size, volume, units, amount or risk) is never auto-traded and is recorded as a signal. 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.

Can an alert close a Binance position?

No. PipSync does not close positions from TradingView alerts: exits happen by stop loss, take profit or by you. 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. While a position in the same instrument opened by a TradingView alert is still open, a new alert for that instrument is not traded automatically, in either direction; an opposite-direction alert is held as a likely strategy exit and recorded as a signal. Exits stay with you on Binance.

What permissions does the Binance API key need?

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 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 and, with auto-trade on, trigger trades. Keep it out of public Pine scripts and shared screenshots, and regenerate it under Settings → Advanced → TradingView Alerts if you suspect a leak.

Parse for free, execute on a paid plan

Connect a signal source and watch PipSync parse in real time. Start on the Free plan at $0 with no card, or subscribe from $24/month for execution — charged at checkout, cancel any time.

Billed at checkout · Cancel any time · Free plan available

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.

FAQ

Frequently asked questions

Yes. Webhook notifications are a feature of TradingView's paid tiers; the free TradingView plan cannot send webhook alerts. PipSync's webhook integration needs a plan that includes it (the Advanced plan).

Written by the PipSync team · Reviewed by PipSync Editorial, Editorial team · Published · Last updated

PipSync is a cloud-based signal automation platform that routes trading signals from Telegram, Discord, TradingView alerts and custom webhooks to broker accounts on MetaTrader 5, cTrader, Match-Trader, Binance Futures and Bybit — with server-side risk management and no VPS required. PipSync is an execution tool, not a signal provider and not investment advice.

PipSync is a signal execution tool. It does not provide trading signals, does not guarantee any trading results and is not investment advice. Trading leveraged products involves substantial risk of loss. See the full risk disclosure and performance disclaimer.