How to Set Up TradingView Webhook Alerts (Step-by-Step)

Close-up of a screen showing red and green candlesticks beside price levels and a market watchlist.

Image Source : Unsplash / Tötös Ádám

This guide walks through connecting a TradingView alert to your MetaTrader terminal using a webhook and PineConnector, so a chart-based signal can trigger a trade without you copying it over by hand. It covers the parts of the setup that are generic to any TradingView webhook, and the parts that are specific to PineConnector's message syntax and bridge, so you know which behavior comes from which system.

Before You Start

A TradingView account with webhook-capable alerts. TradingView's free Basic plan does not include webhook notifications, and TradingView requires two-factor authentication enabled on your account^[1] before it will send any webhook.
A PineConnector account with an active License ID. This is found in your PineConnector portal under Connections.
A receiving side ready to execute trades: either a MetaTrader 4 or MetaTrader 5 terminal running with the PineConnector EA attached to a chart, or a PineConnector Edge instance.
The PineConnector webhook URL: https://webhook.pineconnector.com

How TradingView Webhooks Work with PineConnector

A webhook sends information from one application to another. When a configured alert triggers and its notification settings permit delivery, TradingView attempts to send the message as an HTTP request to the chosen URL. A condition being true does not by itself prove webhook delivery. Per TradingView's own webhook resubmission policy^[2], a receiving server's 5xx error other than a 504 timeout can cause up to three additional attempts, five seconds apart.

PineConnector's part starts once that message reaches https://webhook.pineconnector.com. It processes the message under PineConnector Syntax and the configured setup. The EA requests the broker action. Delivery, processing and broker execution are separate stages, and their timing can vary. Check the broker result rather than treating receipt as a completed trade.

Step 1: Prepare Your MetaTrader Terminal

If you're running your own MT4 or MT5 terminal rather than a PineConnector Edge instance, download the PineConnector Expert Advisor (EA) and install it on the terminal. Drag and drop the EA onto the chart of the instrument you want to trade.

Confirm that Algo Trading / AutoTrading is enabled for the intended self-hosted terminal and that the EA has the required trading permissions.^[7] Disabling automated trading restricts EA trading requests; it does not establish that upstream alerts or webhook delivery stopped. Use the current supported PineConnector EA from your portal's Downloads tab.

If you're using PineConnector Edge instead, your instance is set up and updated through the portal rather than a local MetaTrader install. Follow the Edge setup instructions in your portal for this step.^[6]

Step 2: Master the Automated Risk Syntax

Choose the sizing method that matches your written strategy and verify its units. The following is an illustrative message for TradingView's Message field, not a recommended risk level. Use a License ID connected only to the intended demo account(s), replace LicenseID, and replace EURUSD with the exact broker symbol. If Signal Authentication is enabled, add secret= with the exact case-sensitive key configured for that License ID. Keep the key private.

LicenseID,buy,EURUSD,vol_pct_bal_loss=1,sl_pips=50,tp_pips=100

Each component of this syntax serves a specific purpose:

LicenseID: Identifies the PineConnector connection. Confirm every account attached to it is intended to receive this test.
Action: The direction of the trade (e.g., buy or sell).
Symbol: The specific pair you are trading, such as EURUSD.
Risk Parameter: vol_pct_bal_loss=1 uses 1% of account balance as the planned loss-at-stop sizing input. It is not a maximum-loss limit. Costs, volume constraints, slippage and gaps can change the actual loss.
Stop Loss: sl_pips=50 requests a stop at a distance of 50 PineConnector pips, where one PineConnector pip is 10 symbol quoting points. Explicit pip values take priority over corresponding legacy inputs; other EA filters and broker rules still apply. Check the resulting broker protection.
Take Profit: tp_pips=100 requests a target at a distance of 100 PineConnector pips. A message alone does not prove that the broker accepted either protective level.

This message format, LicenseID,Command,Symbol,Parameters, is specific to PineConnector; it is not part of TradingView itself. You can visit the PineConnector Syntax Guide^[3] for the full list of parameters.

Step 3: Configure the TradingView Alert

With your terminal or Edge instance prepared and your syntax ready, create the alert on TradingView. Open the "Create Alert" dialog for your chosen indicator or strategy. This dialog and its tabs are TradingView's own interface, and only the text you paste into the Message box is PineConnector-specific.

Condition: Select the specific crossover or price level that triggers your entry.
Notifications Tab: Check the box labeled "Webhook URL".
URL Field: Paste the official URL: https://webhook.pineconnector.com
Settings Tab: Navigate to the "Message" box and paste your syntax command.
Notification schedule: Set it to 24/7 (Always Active) for an alert that sends instructions to PineConnector. 24/7 is TradingView's default, but the dialog carries over your last-used schedule where applicable and a preset can apply a saved one, so check it on every alert. Since July 2026 an alert can carry a notification schedule, and outside its active hours TradingView records the trigger in the log but blocks every notification channel, including the webhook^[4]. See how notification schedules affect webhooks.
Alert presets: If you start from a saved preset, check the webhook after applying it. TradingView does not save webhook URLs in alert presets^[5], and it does not say whether the Webhook URL box stays ticked, so tick it if needed and enter https://webhook.pineconnector.com before you create the alert. See what alert presets save.

Saving the alert configures its webhook; it does not confirm that the message reached PineConnector or that the broker executed an instruction. Use the checks in "Verify It Worked" below to confirm each stage.

Step 4: Infrastructure for 24/7 Execution

Automation only works while your terminal is running and connected. If you want it running when your own computer is off, host your MetaTrader terminal on a Virtual Private Server (VPS), or use a PineConnector Edge instance, which is hosted for you. You do not need to leave TradingView or your browser open either way: TradingView fires alerts from its own servers, independent of whether your browser is open.

If you do use your own VPS, such as one from ForexVPS (affiliate link), choose a location close to your broker's server. A shorter physical distance reduces the network path between your terminal and your broker, which is one factor, alongside your broker's own spread and execution, in how closely your fill matches the price your TradingView alert intended. To see which server location is closest to your broker, try a broker latency checker (affiliate link): pick your broker and it lists the lowest-latency location.

Other Risk Parameters Worth Knowing

Beyond the risk syntax in Step 2, PineConnector's parameter set includes a spread filter and a breakeven setting. The spread filter (spread=) rejects a trade if the current spread exceeds the value you set, which is useful around volatile news releases. The breakeven setting (betrigger= paired with beoffset=) moves your stop loss once price has moved a set number of pips in your favor. Both are optional additions to the same message syntax from Step 2. See the PineConnector Syntax Guide for the exact accepted values and how to combine them with the risk parameters above.

Verify It Worked

Setting up the alert and PineConnector configuration is not the same as confirming the chain works end to end. For the full verified-demo-trade procedure, including what to check in MetaTrader and in your PineConnector logs, see our complete TradingView-to-MT5 connection guide^[8]. If your alert fires on TradingView but no trade appears in MetaTrader, this troubleshooting guide walks through the most common causes in order.

Verification checks: receipt and execution are separate
Check	Evidence to confirm
Alert	Find the expected trigger in TradingView's Alerts log^[1].
Delivery	Read Webhook status. Check the URL and notification schedule if delivery is missing^[1]^[4].
Message	Match your License ID, command, broker symbol and parameters to PineConnector Syntax^[3].
Terminal	Confirm the connection and inspect the terminal logs. Edge logs are in Portal → Edge^[6].
Broker	Check the demo order result. Verify accepted orders, fills and positions separately^[8].

Bringing It Together

Automation does not change your strategy's edge. It can reduce manual entry steps, but delivery, EA permissions and broker conditions still affect whether an instruction is executed.

PineConnector relays the instructions you configure. This is not managed execution: you supply the broker connection and the parameters, and you remain responsible for the account. You keep your analysis on TradingView and your execution on MetaTrader, connected by the webhook and syntax covered above. Confirm the connection with a demo trade (see "Verify It Worked" above) before relying on it for a live account.

Delivery, EA trading permissions and the illustrative demo message were reviewed 24 September 2026 against official sources captured 23 September 2026. This review covered recipient scope, authentication, sizing units and requested stop and target levels. No alert, webhook or trade was executed for this review.

Sources

TradingView Help Center – How to configure webhook alerts, accessed 23 September 2026.
TradingView Help Center – Webhook resubmission, accessed 23 September 2026.
PineConnector Docs – PineConnector Syntax, accessed 23 September 2026.
TradingView Help Center – Notification schedule for alerts, accessed 23 September 2026.
TradingView Help Center – Alert presets, accessed 23 September 2026.
PineConnector Docs – Connect your MT5 account, accessed 23 September 2026.
MetaQuotes – MetaTrader 5 Help: Algorithmic trading, accessed 23 September 2026.
PineConnector Docs – Test your setup, accessed 23 September 2026.

PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.

Item added to your cart