TradingView webhook → broker: end-to-end automation.

You designed a strategy in Pine Script and you want it to trade on its own. But TradingView does not execute orders at your broker directly (except through native integrations). The bridge is the webhook: the alert fires, sends a message to a server of yours, and that server executes the order through the broker's API. This guide builds that entire pipeline — and is honest about where it can break.

01The end-to-end architecture

There are four links. Understanding the flow is essential before writing a single line:

02Step 1: the alert in TradingView

In your Pine Script, you use alert() with a JSON message (so the server can interpret it). Then, when creating the alert in the interface, you paste your webhook URL into the "Webhook URL" field.

// in Pine Script — message structured as JSON
if ta.crossover(ma_rapida, ma_lenta)
    alert('{"segredo":"MEU_SEGREDO","acao":"COMPRA","ativo":"BTCUSDT","qtd":0.01}',
          alert.freq_once_per_bar_close)

The segredo is vital — it is what stops anyone who discovers your URL from firing fake orders. We will look at the validation on the server side.

03Step 2: the receiving server

A simple Python server with FastAPI that receives the webhook, validates the secret and processes it:

# servidor.py
from fastapi import FastAPI, Request, HTTPException
import os

app = FastAPI()
SEGREDO = os.getenv("WEBHOOK_SECRET")   # never hardcode it

@app.post("/webhook")
async def webhook(request: Request):
    dados = await request.json()

    # 1. validates the secret — blocks fake requests
    if dados.get("segredo") != SEGREDO:
        raise HTTPException(status_code=403, detail="Não autorizado")

    # 2. parses the signal
    acao  = dados.get("acao")
    ativo = dados.get("ativo")
    qtd   = dados.get("qtd")

    # 3. executes at the broker (function from your execution module)
    if acao == "COMPRA":
        executar_compra(ativo, qtd)
    elif acao == "VENDA":
        executar_venda(ativo, qtd)

    return {"status": "ok", "acao": acao}

The executar_compra function uses the broker's API — exactly the code we showed in the Binance tutorial or in the MT5 API. The webhook only replaces the part that "decides" — now Pine Script is what decides.

04Step 3: where to host the server

The server needs a public URL and has to be online at all times. Options:

• VPS (the same one as the bot) — full control, a fixed IP so you can filter traffic. See our VPS guide.
• Deploy platforms (Render, Railway, Fly.io) — they get the server up fast and have a limited free tier. Good for testing.
• Local tunnel (ngrok) — for testingonly; it temporarily exposes your local PC. Never for production.

05Webhook vs. native integration

Before building this whole pipeline, consider the alternative: some brokers have native TradingView integration — you send orders straight from the chart, with no server in between. Pepperstone is one example. Compare:

• Webhook + server: flexible (it works with any broker that has an API), but it adds points of failure (server, latency, security) and requires maintenance.
• Native integration: simpler and more reliable (no server of yours in the middle), but limited to the brokers that offer it and to what the integration allows.

06The honest risks of webhook automation

Practices that reduce the risk: log every request received and every order sent; implement idempotency (each alert has an ID, ignore repeats); have a "kill switch" (a way to shut everything down fast); and — always — test the whole pipeline on a demo account for weeks before going live.

07Frequently asked questions