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

TradingView can fire webhooks but cannot hold exchange API keys or place orders. PipSync sits in between, and Telegram and Discord signals executed on Bybit use the exchange's unified margin model (one Unified Trading Account, one trade-scoped API key). Every valid TradingView alert lands as a signal on the Signals page, where you review it; auto-trade from TradingView is opt-in, and on Bybit accounts it does not trade alerts for now.

1. 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). It covers wiring up and testing this route; webhook alerts are a paid TradingView feature, so TradingView bills separately.

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 containing a secret token and shows it only once. Treat it like a password: anyone holding 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. 3

   Bybit for Telegram and Discord signals

   TradingView alerts are not auto-traded on Bybit 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 Bybit, create a dedicated key with read and trade permissions (withdrawal off) and add it under Trading Accounts → Add account.

4. 4

   Create the TradingView alerts

   In TradingView (webhook alerts require a paid plan), set the alert condition, paste the JSON payload (instrument, direction, entry, sl, tp1 — with real prices for sl and tp1) into the Message field using placeholders such as {{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. 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. 6

   Test with a few alerts

   Fire the alert once, then open Settings → Advanced → TradingView Alerts and check Recent alerts for its status and any error; a valid alert appears on the Signals page. Check a few real alerts before relying on the setup.

7. 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 Bybit accounts an alert is not auto-traded for now.

Typical setup time: about 12 minutes.

Not by auto-trade, for now. A TradingView alert can send a webhook (an HTTP POST with a message you define), but it cannot store Bybit API keys, size a position or submit an order. PipSync receives the alert at your private webhook URL, validates it and saves it as a signal for you to review. By default it places no order from the alert, and Bybit 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 or keep alive: PipSync's webhook runs server-side the entire time, and every alert received is visible in the dashboard. Telegram and Discord signals still execute on Bybit.

Not on Bybit 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. Bybit 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 Bybit 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. Only JSON alerts can auto-trade, and 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

Use the contract name exactly as Bybit lists it. Bybit's linear USDT perpetuals carry names like BTCUSDT, and PipSync normalises common crypto spellings such as BTCUSD or XBTUSD to BTCUSDT. Unlike MetaTrader forex symbols there are no broker suffixes to guess: the exchange has one canonical name per contract.

The common pitfall sits on the TradingView side. On perpetual charts, the {{ticker}} placeholder resolves with a ".P" suffix — BTCUSDT.P instead of BTCUSDT. A mismatched symbol shows up in Recent alerts as the instrument it was read as, so you can fix the alert before reviewing the signal. Fire a test alert and check how the instrument was read under Recent alerts, or write the literal contract name into the alert message if you want zero ambiguity.

For Telegram and Discord signals executed on Bybit, a Unified Trading Account pools your collateral instead of splitting it across separate product wallets, and PipSync places those orders against the account behind your API key. TradingView alerts are not auto-traded on Bybit for now.

Shared collateral also means positions interact: every open trade consumes margin from the same pool. And remember that leverage and margin mode are settings on your Bybit account, separate from order quantity — PipSync controls what is ordered, not how your account is levered. Review those exchange-side settings before trading.

Exits are not alerts here: PipSync does not close positions from TradingView alerts, and a direction other than buy or sell is rejected. Exits happen by stop loss, take profit or by you, and every payload must carry sl and tp1 prices, which travel with the signal.

One subtlety with strategy placeholders: {{strategy.order.action}} resolves to buy or sell, and a strategy that exits a short technically does so with a buy order. PipSync reads that as a new buy signal, not as a close — so review each signal on the Signals page rather than assuming an exit. 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.

• instrument — the contract name as Bybit lists it, 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

Fire the alert once without waiting for a market condition, then open Settings → Advanced → TradingView Alerts: Recent alerts shows each call with its status and any rejection reason. Valid alerts wait as signals on the Signals page, so you can watch a few real ones arrive and inspect exactly how they were read.

Let the strategy run a handful of alerts and verify instruments and levels match your expectations before relying on it.