Alerts & Automation
How to Configure TradingView Webhook Alerts: Step One to Automation
Webhooks let an alert do more than "call a person" — it can "call a program": when price triggers, TradingView sends an HTTP POST to your URL, and what happens next is up to you — log to a sheet, push to a group bot, or hand off to an order gateway.
Setup
- When creating an alert, check Webhook URL and enter your receiver address (must be a public HTTPS endpoint);
- Write JSON in the message body, injecting live data with placeholders:
{
"ticker": "{{ticker}}",
"price": {{close}},
"time": "{{timenow}}",
"note": "68000 break plan",
"secret": "your-own-passphrase"
}Common placeholders: {{ticker}} symbol, {{close}} trigger price, {{interval}} timeframe, {{timenow}} time; indicator alerts can also use {{plot_0}} for the indicator value.
A minimal receiver
Anything that can receive a POST works: a 20-line Flask/Express service, a Cloudflare Worker, or an off-the-shelf automation platform that turns the webhook into a chat message. Start with "log on receipt," get the pipe working, then talk logic.
Two security lines
- Verify the passphrase: the URL is public and anyone with it can forge a trigger. Carry a secret field in the body and drop anything that fails the check on the receiver;
- Idempotency and rate limits: network retries can deliver the same alert twice; if a webhook leads to real money, the receiver must recognize duplicates and cap executions per unit time.
Honest note: webhook automation hands decisions to rules, and every hole in the rules gets found by the market. Run it against a paper account for at least a month before real money.