A TradingView alert does not place a trade by itself. It fires a notification or sends a webhook, and something on the receiving end has to turn that message into an order on your exchange account through the exchange’s API. That receiver is an automation platform such as Tickerly, which converts your strategy alerts into live orders with no code and no server of your own. This guide walks through the full path, from alert to fill, and shows how to set it up, test it and keep it secure.
Key Takeaways
- A TradingView alert is a message. A webhook receiver connected to your exchange API is what turns it into an order.
- TradingView webhooks only accept URLs on ports 80 and 443, and a request is cancelled if the receiver takes longer than three seconds to respond.
- Never put passwords or login credentials in an alert message, and keep two-factor authentication on for your TradingView account.
- Test on the exchange’s demo account first. Risk rules such as position size and stops belong in your TradingView strategy.
- Tickerly offers a 30-day free trial, with paid plans from $19 per month.
Table of Contents
- Can TradingView alerts trade on an exchange directly?
- How an alert travels from chart to fill
- Which markets and exchanges you can reach
- Step-by-step: connect a TradingView alert to your exchange
- What the alert message should look like
- Troubleshooting alerts that fail, lag or double up
- Security basics for alert-to-exchange setups
- Our perspective
- Start automating your alerts with Tickerly
- FAQ
- Sources
Can TradingView alerts trade on an exchange directly?
Not on their own. An alert is a condition you define: price crosses a level, an indicator flips, or a strategy fires an order event. When it triggers, TradingView can show a popup, send an email, play a sound or, with a paid plan, send an HTTP POST to a webhook URL. That POST carries your alert message as its body.
The exchange never sees that message. Exchanges accept orders only through their own APIs, authenticated with your API keys. So between the alert and the exchange you need an intermediary that does three things:
- Receives the webhook from TradingView.
- Understands what the message asks for (buy, sell, close, which symbol).
- Sends the matching order to your exchange through your API connection.
You can see how this flow fits together in our overview of how automated trading with TradingView works.
How an alert travels from chart to fill
The route has five stops. Knowing them makes every later problem easier to locate.
- Your strategy or indicator evaluates a bar and an order event or condition triggers.
- TradingView’s alert engine takes the alert and builds the message from your template.
- The webhook request goes out to the receiver’s URL.
- The automation platform reads the message and builds an exchange order.
- The exchange accepts the order through its API and fills it according to the market.
Each stop adds time. The alert-to-order part is where a platform’s engineering matters, and it is the part we focus on at Tickerly: orders go out within a fraction of a second of the alert arriving. The final fill still depends on the exchange and on market liquidity, so what happens after the order leaves is outside any platform’s control. Our page on how orders move from signal to fill breaks the stages down in more detail.
Which markets and exchanges you can reach
What you can automate depends on the platform you route through, not on TradingView. Tickerly is built for crypto, forex, stocks, futures and prop firm markets, and it connects to exchanges and brokers through their APIs. It also supports MetaTrader 4 and 5. For MetaTrader, your own MetaTrader terminal must be running, because that is the component that places the order at your broker.
For the current list of supported exchanges, check the automated trading exchanges page rather than relying on any article, since support changes over time. If you trade on KuCoin, there is a dedicated walkthrough for the TradingView to KuCoin setup. If you trade forex or CFDs through a broker, read how to connect TradingView alerts to MT5.
Order actions are limited by what your alert message can express and by what your platform supports. Keep your strategy logic simple and in TradingView: entries, exits and reversals are the actions most strategies need.
Step-by-step: connect a TradingView alert to your exchange
The exact screens differ by platform, but the sequence is the same.
1. Prepare the exchange account
Create an API key on your exchange with only the permissions you need. Trading permission is required for placing orders. Withdrawal permission is not needed for automated trading, so leave it off. If the exchange offers a demo or testnet account, create keys there first. Tickerly’s exchange setup guide covers adding the connection, and My Exchanges is where connected accounts live.
2. Finalize the strategy in TradingView
Position size, stop levels and any exit rules are defined in your Pine Script strategy or indicator, not in the automation platform. Decide those before you create the alert. If you run several symbols, read about multi-symbol strategies and repainting so your alerts fire on confirmed conditions.
3. Create the alert with a webhook
Open the alert dialog on your chart, pick your strategy or condition and enable the webhook URL option in the notifications tab. Paste the URL your automation platform gives you. Then put the message provided by your platform into the message box. Use the message format your platform documents, and do not improvise fields. Tickerly’s walkthrough for automating trading on TradingView shows the exact steps.
4. Respect TradingView’s webhook rules
TradingView sets hard limits on webhooks, and they explain many failures:
- Webhook URLs must use port 80 or 443. Requests to other ports are rejected.
- If the receiving server takes longer than three seconds to process a request, TradingView cancels it.
- IPv6 is not currently supported for webhooks.
- If the message is valid JSON, the request is sent with an application/json content type. Otherwise it is sent as plain text.
Those limits are one reason a hosted receiver is practical: it is already built to accept TradingView requests quickly. If you build your own endpoint instead, you take on keeping it up, fast and reachable around the clock. With Tickerly you need no VPS and no code for TradingView and crypto or exchange connections.
5. Run it on a demo account
Before real money, point the connection at your exchange’s demo account and let the strategy fire several alerts. Check that each alert produced the order you expected: right symbol, right side, right size from the strategy. Tickerly has no paper-trading mode of its own, so the exchange’s demo account is the way to rehearse. Then switch to your live keys.
What the alert message should look like
The message is the instruction. Two points matter:
- Keep it valid JSON if your platform expects JSON. A stray comma or an unquoted value breaks parsing, and the request goes out as plain text instead.
- Use TradingView’s placeholders for dynamic values. They are filled in when the alert fires, so the same template serves every bar.
For Tickerly, copy the message format from your Tickerly dashboard and keep to the fields it provides. Do not add your own settings. If you are building strategies in Pine Script, our guide to TradingView strategy automation from alert to live order shows how strategy order events map onto the alert.
If you run hedge mode on a futures account, there is a separate page on how to set hedge mode alerts.
Troubleshooting alerts that fail, lag or double up
When something goes wrong, work backward along the route.
The alert never fired. Check the alert in TradingView first. Alerts can expire, be deleted, or sit on a condition that never evaluates the way you expect. Our page on missing TradingView alerts lists the usual causes.
The alert fired but nothing arrived. Look at the webhook URL, the port and the three-second cutoff described above. A receiver that responds slowly can cause TradingView to cancel the request.
The order arrived late. Separate the stages. Alert generation on TradingView, delivery, order creation and the exchange fill each add time. Fills on thin markets can differ from the price you saw on the chart. For a structured way to think about timing, see measuring real-time execution.
You got two orders. Duplicates often come from two alerts on the same condition, a strategy and an indicator both firing, or an alert that was created twice. Review your alert list and remove overlaps. Our pages on webhook retries and the secure crypto TradingView bot setup go deeper on how duplicates arise.
Keep a simple log while you test: time the bar closed, time the order showed on the exchange, and the fill price. Reviewing it later is easier when you know how to find your own trading mistakes in a systematic way, separating process errors from market noise.
Security basics for alert-to-exchange setups
A webhook is a door between TradingView and your money, so treat it with care.
- Never put credentials in the message. TradingView’s guidance is to keep logins and passwords out of the webhook body. API keys belong in your automation platform’s exchange connection, not in the alert text.
- Keep two-factor authentication on. TradingView requires 2FA to use webhook alerts, and it protects the account that can trigger your orders.
- Limit API key permissions. Enable trading, disable withdrawals.
- Store keys properly. The reasoning behind safe webhook endpoints and keeping keys out of exposed places applies to any integration that handles crypto.
We cover this further in TradingView webhook security.
Our perspective
We built Tickerly around one idea: the strategy you already trust in TradingView should be the thing that trades, and the connection between chart and exchange should be quick and simple. Most traders we talk to do not want to run a server, maintain a script or learn webhook plumbing. They want their Pine Script alert to become an order at their exchange or MetaTrader terminal.
That is why setup is no-code, why one account can handle many strategies and alerts, and why execution is designed to leave the platform within a fraction of a second of the alert. Timing matters because fleeting opportunities do not wait, and emotion-free automation keeps your rules consistent whether you are at your desk or asleep.
Your strategy remains yours. Sizing, stops and exit logic live in TradingView, where you can see and change them. We handle the routing.
Jay
Start automating your alerts with Tickerly
If you are ready to turn your TradingView alerts into live orders, Tickerly connects your strategies to supported exchanges and MetaTrader without a VPS or coding for TradingView-to-exchange routing. Every account starts with a 30-day free trial.
Paid plans are priced per month: Level 2 is $19, Level 3 is $29 and Level 4 is $39. Level 4 Ultra is also available for higher needs. Plans differ by supported asset classes, number of strategies and alert limits, so compare them on the Tickerly plans page. For help picking a webhook service, see our overview of TradingView webhook services.
FAQ
Do I need a paid TradingView plan to send alerts to an exchange?
Webhook alerts are a feature of paid TradingView plans, and they also require two-factor authentication on your account. Check TradingView’s current pricing page for which tier suits you. The alert itself is free to create, but the webhook delivery is what connects it to your exchange.
Can I send alerts to more than one exchange?
Yes, if your automation platform supports multiple connections. You can run different strategies on different accounts and assets. Our page on a multi-exchange trading bot approach explains how traders organize this.
Why did my alert fire but no order appear?
Start with the webhook URL, since TradingView only accepts ports 80 and 443 and cancels requests that take over three seconds. Then confirm your exchange connection is active and your API key has trading permission. If it still fails, review our automated trading FAQ.
Can I test without risking real money?
Yes. Use your exchange’s demo account and connect demo API keys, then run the strategy through several alerts. Check each order against what your strategy intended before moving to live keys.
Sources
- How to configure webhook alerts, TradingView Help Center
- Webhooks and Idempotency: Building a Reliable Crypto Integration, CryptoPayr Blog
- Trading Error Detection: How to Find Your Own Mistakes
Recommended
- TradingView Strategy Automation: How to Go From Alert to Live Order
- TradingView Bybit Futures: How to Automate Your Alerts
- TradingView to MT5: How to Connect Alerts and Automate
- How to Connect TradingView to MT4 for Automated Trading
This article was produced with Al assistance and reviewed for accuracy. It is provided for general information only and is not professional or financial advice.