TradingView alerts to Hyperliquid: webhook setup, step by step

How the pieces fit

TradingView cannot place orders on Hyperliquid by itself. It can send a webhook: an HTTP request with a message you define, fired every time an alert triggers. TensorTrader receives that webhook, checks the secret, normalizes the symbol, sizes the position, clamps leverage to the lower of your policy and Hyperliquid's maximum, and signs the order with your Hyperliquid agent key. After the fill it places stop-loss and take-profit orders and keeps reconciling the position with the exchange.

You set this up once: an agent wallet on Hyperliquid, a webhook secret in TensorTrader, and alerts on TradingView that carry that secret. The extension writes the alerts for you, so you rarely touch the webhook message by hand.

Step 1: connect Hyperliquid

1. 1Settings, Exchange Auth, Hyperliquid, Connect Wallet.
2. 2Choose the testnet card to start.
3. 3Approve the TensorTrader agent in MetaMask and wait for the green status.

Step 2: build the alerts

The extension checks your existing alerts first and skips any that already exist, creates each new alert exactly once, and finishes with a reconciliation sweep that removes accidental duplicates.

1. 1Open a TradingView chart and the TensorTrader extension side panel.
2. 2In Batch Create, step 1 · Exchanges, select your Hyperliquid key.
3. 3In step 2 · Tokens, type base tokens one per line: BTC, ETH, SOL. Quote suffixes like USDT are stripped for you.
4. 4In step 3 · Signal source, press Load favorites and pick an indicator or strategy from your TradingView favorites.
5. 5Set timeframes in DCA Across Timeframes, then leverage mode and risk handling.
6. 6Review the plan roster and press Create N alerts.

Step 3: understand the message

Every alert carries a JSON message that TensorTrader renders per alert. In Guided mode you never edit it. In Advanced mode you can, and the wizard validates the JSON and keeps TradingView placeholders such as {{ticker}} and {{close}} intact while filling TensorTrader variables such as {{tt.leverage}} for each alert.

{
  "secret": "{{tt.secret}}",
  "a": "{{tt.action}}",
  "sym": "{{ticker}}",
  "tf": "{{interval}}",
  "exchange": "hyperliquid",
  "exk": "{{tt.exchange_key_id}}",
  "px": "{{close}}"
}

Step 4: watch the first fills

Keep the first batch small: a few tokens on one timeframe. When an alert fires, the signal appears in the TensorTrader signal queue, then as an open position with its protective orders, and finally as a closed trade with profit and fees booked from Hyperliquid's own fills. If an alert does not arrive, check that the alert is active on TradingView, that its message still contains the secret, and that trading is enabled for your account.

Hyperliquid perps settle in USDC, trade around the clock and have a published maximum leverage of 50x on the largest markets, lower on others. TensorTrader never exceeds the venue maximum for the market, and your own policy is usually much lower.

Common mistakes

secret left out

Custom JSON without {{tt.secret}} is rejected. Rotate the secret if it ever appears in a public script.

wrong network

Testnet alerts hit a testnet key; a mainnet key needs its own mainnet approval.

duplicate alerts

Creating alerts by hand next to a batch can double orders. Let Batch Create own the set.

too many at once

Start small; TradingView plans cap concurrent alerts (Essential 20, Plus 100, Premium 400, Ultimate 1,000).

Indicator alerts vs strategy alerts

If your TradingView script is an indicator with alertconditions, Batch Create makes one alert per direction per token: an "open long" alert and an "open short" alert, each mapped to the script's matching condition in Variable alignment. If it is a strategy, one alert per token follows the strategy's own entries and exits, and TradingView's {{strategy.order.action}} tells TensorTrader whether each fill is a buy or a sell. Strategies are usually easier to automate cleanly because exits are part of the script.

• alertcondition() vs alert() vs strategy alerts →

What TensorTrader checks on every webhook

1. 1The secret matches your account; anything else is dropped.
2. 2The message fields are on the allow-list; unknown keys are ignored.
3. 3The symbol maps to a Hyperliquid perpetual; unlisted symbols are rejected, not guessed.
4. 4Leverage is clamped to the lower of your policy and the market’s maximum.
5. 5Your account has trading enabled and enough free margin; otherwise the signal is recorded, not executed.

Frequently asked questions

Can TradingView trade Hyperliquid directly?

No. TradingView sends webhooks; a bridge such as TensorTrader turns them into signed Hyperliquid orders.

Which TradingView plan do I need for webhooks?

Webhook alerts need a paid TradingView plan. The plan also caps how many alerts you can run at once.

Do strategy alerts work?

Yes. Strategy alerts pass {{strategy.order.action}} so the direction comes from the strategy itself.

Keep reading

• Hyperliquid trading bot: how to automate Hyperliquid perps safely

  The complete guide to automating Hyperliquid: agent wallets, testnet, TradingView and GoCharting alerts, leverage and margin, fees and funding, portfolio mode, and the real results of our own testnet books.

• TradingView webhook JSON explained: every placeholder you can use

  What a TradingView webhook message is, which {{placeholders}} TradingView fills in, which variables TensorTrader adds, and a working JSON template for automated orders.

• What is a Hyperliquid API (agent) wallet, and is it safe?

  A Hyperliquid API wallet is a separate key your main wallet authorizes to trade but never withdraw. Here is how it works, what it can and cannot do, and how TensorTrader creates one without ever seeing your seed phrase.

• Batch Build: strategies, indicators and multi-condition alerts in the TensorTrader extension

  How the extension's Batch Create wizard turns one indicator or strategy into dozens of TradingView alerts: signal sources, AND-combined indicators, variable alignment, DCA across timeframes, leverage modes and duplicate-proof runs.