How to Auto-Execute TradingView Alerts on Bybit (Free Setup Guide)

If you're running a strategy on TradingView and still placing trades by hand, you're leaving money on the table. The seconds between an alert firing and you opening Bybit, typing in the symbol, setting the leverage, and hitting buy — that delay costs real money. In fast-moving crypto markets, a 30-second delay can mean 1-3% worse entry on a volatile coin.

This guide walks you through automating TradingView alerts on Bybit using webhooks, so your strategy executes the moment it triggers. No coding required. We'll cover everything from creating API keys to testing your first automated trade.

Why Manual Execution Costs You Money

Let's run the numbers on why automation matters. Say your TradingView strategy fires an alert on ETHUSDT at $3,200. By the time you:

1. Hear the alert notification (if you're awake)
2. Open your phone or computer
3. Log into Bybit
4. Find the right trading pair
5. Set leverage, order type, and size
6. Double-check and submit

... 30 seconds to 2 minutes have passed. On a coin moving 0.5% per minute, that's $16-$64 of slippage on a single $3,200 entry. Multiply that by 5-10 trades per day, and you're losing $80-$640 daily just to execution delay. That doesn't even account for the trades you miss entirely because you were sleeping, working, or in the shower.

How TradingView Webhooks Work

TradingView webhooks are the bridge between your chart analysis and your exchange. Here's the flow:

1. Your strategy or indicator fires an alert on TradingView
2. TradingView sends an HTTP POST request (the webhook) to a URL you specify
3. A middleware server receives that webhook, parses the trade details, and calls the Bybit API
4. Bybit executes the trade within milliseconds

The critical piece most people miss: TradingView doesn't connect directly to Bybit. You need something in the middle to translate the webhook into an API call. That's where tools like CryptoScope AI come in — it acts as the middleware that receives your webhooks and executes them on Bybit instantly.

Step-by-Step Setup

First, you need API credentials that allow the middleware to place trades on your behalf.

1. Log into Bybit and go to Account → API Management
2. Click Create New Key
3. Select System-generated API Keys
4. Name it something like "TradingView Bot"
5. Under permissions, enable: Read-Write for Contract > Order and Contract > Position
6. Optionally restrict to your server's IP address for extra security
7. Save your API Key and Secret somewhere secure — you won't see the secret again

You need a webhook endpoint that's always online and ready to receive TradingView's POST requests. If you're using CryptoScope AI, your webhook URL will look something like:

https://signalbot.cryptoscopeai.com:3000/api/webhook/tradingview?userId=YOUR_USER_ID

After connecting your Bybit API keys in the CryptoScope AI settings page, the app generates a unique webhook URL for your account. Copy this URL — you'll paste it into TradingView in the next step.

This is where most people make mistakes. The alert message body needs to be valid JSON that the middleware can parse. Here's the format CryptoScope AI expects:

{
  "action": "{{strategy.order.action}}",
  "symbol": "{{ticker}}",
  "price": "{{close}}",
  "quantity": "{{strategy.order.contracts}}",
  "orderType": "market",
  "leverage": "10",
  "takeProfit": "{{plot_4}}",
  "stopLoss": "{{plot_5}}"
}

Here's what each field does:

• action — "buy" or "sell", pulled automatically from your strategy's order direction
• symbol — The ticker (e.g., ETHUSDT), auto-populated from the chart
• price — Current close price at time of alert
• quantity — Number of contracts from your strategy's position sizing
• orderType — "market" for instant execution, or "limit" if you want to set a specific price
• leverage — Bybit leverage multiplier
• takeProfit / stopLoss — Can be hardcoded values or pulled from plot outputs in your Pine Script

To create the alert in TradingView:

1. Right-click on your chart → Add Alert (or press Alt+A)
2. Set the condition to your strategy or indicator
3. In the Notifications tab, check Webhook URL and paste your URL
4. In the Message field, paste the JSON template above
5. Click Create

Before going live, always test with paper money. CryptoScope AI has a built-in paper trading mode that simulates execution using real-time Bybit prices without risking capital. Enable it in Settings, trigger a test alert, and verify:

• The correct symbol is traded
• Entry price matches the alert price (within normal spread)
• Take profit and stop loss levels are set correctly
• Position size matches your configuration

Run paper trades for at least 24-48 hours before switching to real money. Watch for any parsing errors in the trade logs.

Common Mistakes (and How to Avoid Them)

1. Wrong API Permissions

If you only enabled "Read" permissions, the bot can check prices but can't place orders. You need "Read-Write" specifically for Contract trading. If you're trading spot, enable spot order permissions instead.

2. Incorrect Symbol Format

Bybit uses specific symbol formats. ETHUSDT works, but ETH/USDT or ETH-USDT won't. Make sure your TradingView chart is set to the Bybit exchange data feed, so {{ticker}} outputs the correct format. If you're using a different data feed, hardcode the symbol in your JSON.

3. TradingView Plan Limitations

Webhooks are not available on TradingView's free plan. You need at least the Essential plan (previously called Pro). If you don't see the webhook option in your alert settings, upgrade your plan first.

4. Invalid JSON in Alert Message

A single missing comma or extra quote breaks the entire webhook. Always validate your JSON at jsonlint.com before saving your alert. The most common issue: trailing commas after the last field.

5. Insufficient Balance

Your bot will try to execute but fail silently if your Bybit account doesn't have enough margin. Always keep a buffer — if your strategy uses $500 per trade with 10x leverage, make sure you have well over $50 in available margin to account for fees and price movements.

Why Use Middleware Instead of Direct Integration?

You might wonder: why not connect TradingView directly to Bybit? The answer is that TradingView doesn't support direct exchange connections for webhooks. It sends a generic HTTP request — it doesn't know what a Bybit API call looks like.

A middleware solution like CryptoScope AI adds several advantages beyond basic translation:

• Trade logging — Every webhook received and every order placed is recorded, so you can debug issues
• Position management — Automatic TP/SL placement, trailing stops, and DCA on dips
• Portfolio view — See all your automated trades alongside manual trades in one dashboard
• Paper trading — Test without risking real funds using live market prices
• Multiple strategies — Run several TradingView strategies simultaneously with separate position sizing

What Happens After Setup

Once everything is connected, the workflow is fully hands-off:

1. Your TradingView strategy identifies a trade setup
2. An alert fires and sends the webhook (typically under 1 second)
3. CryptoScope AI receives it, validates the JSON, and calls the Bybit API
4. The trade executes on Bybit with TP and SL already set
5. You get a Telegram notification confirming the trade
6. The position is monitored and closed automatically when targets are hit

You go from "staring at charts waiting for alerts" to "checking your trade history at the end of the day." The strategy does its job 24/7, whether you're sleeping, working, or on vacation.