TradingView to Bybit — automate your strategy end to end

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.

TradingView can fire webhooks but cannot hold exchange API keys or place orders. PipSync is the execution layer in between, and on Bybit it works with the exchange's unified margin model: one Unified Trading Account, one collateral pool, one trade-scoped API key. Because both entries and exits travel as alerts, a complete strategy round-trip — open, manage, close — runs without you touching the chart.

1. 1

   Create a free PipSync account

   Sign up at app.pipsync.io — no credit card required. PipSync's free plan covers wiring up and testing this route; the only paid requirement on this route sits on TradingView's side, because webhook alerts are a paid TradingView feature.

2. 2

   Get your PipSync webhook URL

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

3. 3

   Connect Bybit with a trade-only API key

   In Bybit's API management, create a dedicated key with read and trade permissions and leave withdrawal permission off — an execution tool never needs to move funds. Add the key under broker accounts in PipSync; unified margin accounts connect the same way.

4. 4

   Create the TradingView alerts

   In TradingView (webhook alerts require a paid plan), set the alert condition, paste the JSON payload into the Message field using placeholders such as {{strategy.order.action}} and {{ticker}}, and paste your PipSync URL under Notifications → Webhook URL. For full automation, wire alerts to both your entry and your exit conditions.

5. 5

   Set sizing and guardrails

   Either send a fixed quantity in the payload's lots field or let PipSync's server-side risk rules compute the size. Add guardrails — maximum open trades, symbol filters — which are enforced before any order reaches the exchange.

6. 6

   Test, then start small

   Use Send Test Signal on your TradingView source to fire a sample payload and check the parsed result plus the exchange's response. Keep Manual Approval mode on at first so you inspect each trade before it executes, and begin with small size when you go live.

Typical setup time: about 12 minutes.

No — and that gap is exactly what this route fills. 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 against your server-side risk rules, and places the order on Bybit over the exchange's API.

Compared with hosting an open-source bot on a rented server, there is nothing to deploy or keep alive. Crypto derivatives trade around the clock including weekends, so a self-hosted script that crashes unnoticed quietly stops executing your strategy; PipSync's pipeline runs server-side the entire time, and every alert and resulting order is visible in the dashboard.

Use the contract name exactly as Bybit lists it. Bybit's linear USDT perpetuals carry names like BTCUSDT, while its inverse contracts use the coin-margined form such as BTCUSD — two different products, so the payload's symbol field decides which one you trade. 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 is rejected by the exchange rather than misrouted, so the failure is visible, but it still means no trade. Fire a test signal and check the parsed symbol in the PipSync dashboard, or write the literal contract name into the alert message if you want zero ambiguity.

It simplifies it. With a Unified Trading Account, Bybit pools your collateral instead of splitting it across separate product wallets, and PipSync places orders against the account behind your API key. A strategy that rotates across several contracts draws from one margin pool — there are no pre-trade transfers between sub-wallets standing between an alert and its fill.

Shared collateral also means positions interact: every open trade consumes margin from the same pool, so a multi-symbol strategy should be paired with PipSync's max-open-trades cap and symbol filters. 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 turning a strategy loose.

Exits are just alerts too. The payload's action field accepts buy, sell and close: entries arrive as buy or sell, and an alert carrying close flattens the open position on that symbol. You can also attach sl and tp prices to the entry payload so protective levels ride along with the position from the moment it opens.

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. If sized like an entry, that can mean reversing instead of flattening. When an alert is meant to close rather than flip, send the literal action "close" in that alert's message — it removes the ambiguity entirely.

• action — "buy", "sell" or "close" (close exits the open position on that symbol)
• symbol — the contract name as Bybit 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

Two safeguards inside PipSync work regardless of what your exchange account offers. Send Test Signal, on your TradingView source, fires a sample payload without waiting for a market condition and shows you the parsed result plus whether the exchange accepted the order. Manual Approval mode holds every incoming trade for your confirmation, so you can watch a few real alerts arrive and inspect exactly what would be sent before anything executes automatically.

When you do switch the route live, start with small size. Let the strategy complete a handful of full round-trips — entry, management, exit — at a quantity you are comfortable losing while you verify symbols, sizing and exit behavior match your expectations. Only then scale the size up.