TradingView to Binance — execute 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.

A TradingView alert can send a webhook but cannot hold exchange API keys or place orders by itself. PipSync is the execution layer in between: it receives the alert, applies your sizing and risk rules, and submits the order to Binance over the exchange's API. 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 a free PipSync account

   Sign up at app.pipsync.io — no credit card needed. The free plan covers adding a TradingView webhook source and connecting an exchange account, so you can wire up and test this route before paying anything.

2. 2

   Get your PipSync webhook URL

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

3. 3

   Connect your Binance Futures account

   On Binance, create a dedicated API key for PipSync with futures trading enabled and withdrawals disabled — an execution tool never needs withdrawal rights. Add the key under broker accounts in PipSync and select the futures account to execute on.

4. 4

   Create the TradingView alert

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

5. 5

   Set sizing and guardrails

   Decide whether the alert carries a fixed quantity or whether PipSync's server-side risk rules compute the size. Add guardrails such as maximum open trades and symbol filters; they are enforced before any order reaches the exchange.

6. 6

   Send a test signal and verify

   Use Send Test Signal on your TradingView source to fire a sample payload without waiting for the market. Check the parsed result and whether the exchange accepted the order, keep Manual Approval mode on at first, and start with small size.

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 that missing execution layer: the alert posts JSON to your private PipSync webhook URL, PipSync validates it against your risk rules, and the order goes to Binance Futures over the exchange's API.

This replaces the usual do-it-yourself route of hosting an open-source trading script on a rented server. There is nothing to deploy, patch or keep alive, which matters in crypto: the market trades around the clock, including weekends, and a self-hosted process that dies unnoticed simply stops executing your strategy. PipSync's pipeline runs server-side the whole time.

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 the parsed symbol 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.

• action — "buy", "sell" or "close" (close exits the open position on that symbol)
• symbol — the instrument name as the exchange lists it, e.g. BTCUSDT
• price — entry price; 0 means execute at market
• sl / tp — stop-loss and take-profit levels; 0 omits them
• lots — optional fixed quantity that overrides your risk rules for this one trade
• comment — optional free-text tag shown on the resulting trade

Binance USD-M futures are sized in base-asset quantity — a BTCUSDT order is for an amount of BTC — while margin and settlement are in the quote asset (USDT). COIN-M contracts settle in the coin itself. You have two options in PipSync: send a fixed quantity inside the alert payload, which overrides your risk rules for that specific trade, or omit it and let PipSync's server-side rules compute the size — for example percent-risk sizing relative to your account, applied before the order is sent.

Remember that leverage and margin mode are settings on your exchange account, separate from order quantity. The same quantity means very different exposure depending on the leverage you have configured, so review those exchange-side settings before turning a strategy loose — PipSync controls what is ordered, not how your Binance account is levered.

An exit should only ever shrink or close an existing position — never open a new one. PipSync supports Binance Futures' reduce-only flag for exactly this: if your exit alert arrives after the position is already flat (say the exchange-side stop-loss fired first), a reduce-only order is rejected by the exchange instead of silently flipping you into the opposite direction.

In practice you send action "close" from your strategy's exit, and the position on that symbol is closed. Combined with reduce-only semantics, a duplicated or late exit alert cannot turn a flat book into an unintended short. For entries that should never cross the spread, Binance's post-only order type is supported as well.

Create a dedicated API key just for PipSync and enable only what execution requires: futures trading. Leave withdrawals disabled — an execution tool has no business moving funds off the exchange, and 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 to your account. Keep it out of public Pine scripts and shared screenshots, and regenerate it from the Sources page if you suspect exposure.