TradingView Webhook Setup Guide: Automate Alerts to Trades

A TradingView webhook turns a chart alert into an action: when your alert condition fires, TradingView's servers send an HTTP POST request to a URL you specify, carrying a JSON payload that a receiving service reads and acts on — most usefully, by placing a trade. It is the standard bridge between 'my indicator just triggered' and 'an order was submitted,' and it runs without your chart or computer being open, because the alert fires from TradingView's side. This guide covers the exact setup, the payload format, and — honestly — the parts that quietly break in production.

One clarification first, because it trips people up: a webhook only sends a message. It does not place a trade by itself. Something on the other end has to receive that message and translate it into an order on your exchange. That receiver is where all the real engineering, and all the real risk, lives — which is why most of this guide is about the receiving side, not the TradingView side.

Published July 6, 2026.

How a TradingView webhook actually fires

When you attach a webhook URL to an alert, here's the sequence: your condition triggers on TradingView's servers → TradingView sends a POST request to your URL with the alert's message as the body → your endpoint receives it and does whatever you programmed. The crucial detail is that this happens server-side at TradingView. Your browser can be closed, your laptop asleep — the alert still fires. What must be awake is your receiver: the endpoint at the webhook URL has to be reachable 24/7, or the message arrives at a dead address and nothing happens.

Webhook alerts require a paid TradingView plan (the free tier does not expose the Webhook URL field), and each alert can point at one URL. That's the entire TradingView-side model — deliberately simple, because TradingView's job ends the moment the POST leaves its servers.

The JSON payload (and the placeholders that make it dynamic)

By default an alert message is plain text, but almost every automation service wants JSON. If your alert message is valid JSON, TradingView automatically sends it with an application/json content-type — so you just write JSON directly in the message box. The power comes from placeholders: TradingView substitutes live values at fire time. A typical payload looks like {"ticker": "{{ticker}}", "action": "{{strategy.order.action}}", "price": {{close}}} — where {{ticker}} becomes the symbol, {{strategy.order.action}} becomes buy or sell from your strategy, and {{close}} becomes the current close price. The receiver reads those fields and knows exactly what to do.

This is also the single most common failure point. A missing comma, a mismatched field name, or a placeholder your receiver doesn't expect will cause orders to fail — often silently, with no error on the chart. The discipline: match your JSON to the exact schema your receiving service documents, and always test the payload on a paper-trading or testnet endpoint before pointing it at real money.

Step-by-step: creating the alert

The setup itself takes about a minute. Open the alert dialog (the ⏰ icon in the toolbar, or right-click the chart → Add Alert). Set your Condition — a price crossing a level, an indicator value, or a signal from a Pine strategy. Scroll to the Notifications tab and tick Webhook URL, then paste the URL your receiving service gave you. In the Message box, write the JSON payload with the placeholders your receiver expects. Save. That's it — the alert now POSTs to your endpoint every time it triggers (or once, if you set it to fire only once).

Before you rely on it, fire a test. Most receiving platforms show incoming webhooks in a log; trigger the alert manually or set a condition you can force, and confirm the payload arrives and parses. Untested webhooks that 'looked right' are how people discover at 3 a.m. that a field name was wrong.

The receiver problem — where retail automation really breaks

Because the webhook only delivers a message, you need something listening that converts it into an exchange order. There are two broad options, and the choice is the whole game. The first is running your own receiver — a script on a server (a cheap VPS, not your home PC) that holds your exchange API keys, validates the payload, and submits the order. The second is a hosted bridge service that receives the webhook for you and routes to your exchange via keys you've connected.

Two failure modes dominate here. Uptime: a home laptop as a receiver is the number-one point of failure in retail algo trading — it sleeps, loses wifi, or reboots, and the signal vanishes. Use always-on infrastructure. Security: never put credentials, API keys or passwords in the webhook body — the payload is a message in transit, and anything sensitive in it can leak. Keys belong on the receiver, never in the alert. A webhook body should describe the trade, nothing more.

Getting the order onto Hyperliquid — and the safer alternative

To route TradingView alerts to Hyperliquid specifically, your receiver needs to sign Hyperliquid orders. The safety-critical detail is what key it uses: Hyperliquid supports scoped agent keys that can place orders but cannot withdraw funds. A webhook receiver should hold one of those — never a key with withdrawal rights — so that even a compromised receiver or a malformed payload can't drain your wallet. It can only trade. For the full Hyperliquid-specific walkthrough of the webhook-to-exchange bridge and the scoped-key model, see How to Automate Trades from TradingView to Hyperliquid.

The honest alternative is worth stating plainly: the TradingView-webhook path is powerful but fragile — you're maintaining a receiver, a payload schema, uptime and key hygiene, and a single broken link fails silently. If what you actually want is a rules-based strategy trading Hyperliquid 24/7 without running any of that plumbing, a purpose-built platform removes the whole chain. That's the design of Signalview (our product): strategies backtested over 18 months, compressed into one score from −100 to +100, and traded by non-custodial AI agents on scoped keys — no webhook, no receiver, no VPS to keep alive. It's free to run; only Hyperliquid's normal fees apply. See Best Hyperliquid Trading Bots in 2026 for how the approaches compare, and How a Hyperliquid Trading Bot Works for the mechanics.

Risk note: automating trades means orders execute without a human in the loop — a wrong payload, a bad signal or a receiver outage can all lose money, and leverage amplifies every one of them. Test on paper first, start small, and never automate more size than you'd trade by hand.