Guides, manuals and platform references.
This guide explains how to automate TradingView alerts when the direct Webhook URL notification field is unavailable. Direct webhook delivery remains the cleanest method when it is available, but a structured alert can also reach AlgoWay through plain text email.
AlgoWay can receive TradingView alert messages by email. That means your alert can be sent as plain text to a dedicated address such as WebhookUUID@algoway.co. AlgoWay then reads the message, parses the JSON, and routes the instruction to the selected execution platform.
The goal is to send a signal from a TradingView indicator, strategy, or manual alert to an external execution service, then route that signal to MT5, TradeLocker, Binance, OKX, Bybit, Capital.com, cTrader, DXtrade, Match-Trader, or another supported platform.
A standard TradingView webhook sends an HTTP POST request directly to a URL. When direct Webhook URL delivery is not available in your plan or current alert settings, the email route can still deliver the structured alert message to AlgoWay.
This method does not provide an unrestricted direct webhook. It changes the delivery path: TradingView sends the message by plain text email, while AlgoWay receives and processes it through the webhook route connected to that email address.
Both routes can move a TradingView alert into AlgoWay, but they are not identical. The direct webhook route is faster and cleaner. The email route is useful when the goal is to avoid relying on Webhook URL access.
| Route | How TradingView sends the alert | Best use case | AlgoWay role |
|---|---|---|---|
| Direct Webhook URL | TradingView sends an HTTP POST request to the AlgoWay webhook URL. | Best for live automated trading, fast execution, and normal webhook automation. | Receives the POST body, validates JSON, and routes the order to the selected platform. |
| Plain text email | TradingView sends the alert message to WebhookUUID@algoway.co. |
Useful as a TradingView webhook alternative when direct webhook delivery is unavailable. | Receives the email, reads the plain text JSON, and processes it as an AlgoWay signal. |
The workflow is simple. You create a normal AlgoWay webhook, but instead of pasting the Webhook URL into TradingView, you use the webhook UUID as an email destination.
When the alert fires, TradingView sends an email. AlgoWay receives that message, extracts the JSON, and sends the instruction to the platform configured behind that webhook.
Start from the AlgoWay dashboard. Create the webhook exactly as you would for a normal TradingView automation route.
Example format:
e7a19089-f14d-4cc0-ac2c-5379b974e2c4@algoway.co
This address is not your personal mailbox. It is an AlgoWay processing address connected to a specific webhook route.
In TradingView, open account settings and go to the alert delivery area. If your account has alternative email delivery, add the AlgoWay UUID email there.
Format:
YourWebhookUUID@algoway.co
TradingView should send a confirmation message to that address. Since the address belongs to AlgoWay, the verification email appears inside the AlgoWay dashboard.
Open the mail area inside your AlgoWay dashboard. You should see the verification message sent by TradingView. Copy the code and paste it back into TradingView to verify the email address.
The same area can later be used for debugging. If an alert fires and AlgoWay receives the email, you can confirm that the delivery side worked. If the email arrived but no trade was executed, the next thing to check is the JSON message.
Create the alert from your TradingView chart, indicator, or strategy. The alert source can be a normal price condition,
a Pine Script indicator, a strategy order event, or an alert() call.
The important part is the notification method and message body:
AlgoWay needs a structured instruction. That means the TradingView alert message should be JSON, not a casual sentence. The JSON tells AlgoWay which platform route to use, which symbol to trade, what side to execute, how much size to use, and whether stop loss or take profit should be attached.
Common fields include:
platform_nametickerorder_actionorder_contractspricestop_loss / take_profitsl_price / tp_priceTradingView placeholders can be used inside the JSON. AlgoWay receives the final rendered message when the alert fires.
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_action": "buy",
"order_contracts": 0.10,
"stop_loss": 25,
"take_profit": 50
}
{
"platform_name": "tradelocker",
"ticker": "XAUUSD",
"order_action": "sell",
"order_contracts": 1.0,
"sl_price": 2368.50,
"tp_price": 2325.00
}
{
"platform_name": "binance",
"ticker": "{{ticker}}",
"order_action": "{{strategy.market_position}}",
"order_contracts": "{{strategy.order.contracts}}",
"price": "{{close}}"
}
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_action": "flat",
"order_contracts": 999999
}
The same principle applies whether the alert is delivered by direct webhook or by plain text email. The delivery route changes, but the JSON remains the instruction.
The email-based route is a practical fallback, but it is not identical to direct webhook delivery.
| Limitation | What it means | Practical answer |
|---|---|---|
| Availability can change | TradingView may change plan rules, UI names, or which accounts can use plain text alert delivery. | Check your current alert dialog and account settings. |
| Email is not the fastest route | Email delivery can be slower than HTTP webhook delivery. | Use direct webhook for speed-sensitive live execution. |
| One alternative email at a time | The workflow is usually tied to one configured alternative alert email. | Use one AlgoWay route at a time or switch the UUID email when needed. |
| JSON still matters | Email delivery does not fix invalid alert syntax. | Validate the JSON and test with a small demo route before live trading. |
Check your current TradingView alert dialog and account settings. If the option is not available, use the standard AlgoWay Webhook URL route instead.
Confirm that the email address is exactly the webhook UUID followed by @algoway.co. A typo in the UUID means the
message cannot be attached to the right route.
Check the JSON message. The most common reasons are invalid JSON, wrong platform_name, unsupported symbol format,
missing order size, or an order action that does not match the route.
The UUID email identifies the AlgoWay webhook route. If you copied the UUID from another webhook, the signal will go to that route. Use the UUID from the exact webhook you want to trigger.
A direct TradingView Webhook URL depends on TradingView account features and plan rules. This guide explains a practical free webhook alternative: send the TradingView alert by plain text email to AlgoWay when that option is available.
Yes, if your TradingView account allows plain text alert email. Send the JSON alert message to your AlgoWay UUID email, and AlgoWay can process it as an automation signal.
No. A webhook is direct HTTP POST delivery. The email route is an alternative delivery path that still lets AlgoWay receive and process a structured alert message.
Yes. AlgoWay needs JSON to understand the symbol, action, size, platform, and risk parameters.
Direct Webhook URL is better when it is available. The plain text email route is useful when you need a workaround or want to test alert automation without relying on direct webhook access.
Yes. Create an AlgoWay MetaTrader 5 webhook, use its UUID email as the TradingView alert email, and send a valid MT5-compatible JSON message.