Main clusters and core pages.
Manual TradingView webhook alerts let you turn a simple chart condition into an AlgoWay trading command without using a full TradingView strategy. You choose a condition such as price crossing a level, paste a fixed JSON message, enable the AlgoWay webhook URL, and TradingView sends the command when the condition is triggered.
This page is written for traders searching for manual TradingView webhook alert, TradingView price alert webhook, TradingView alert JSON, manual webhook trading bot, TradingView webhook URL, AlgoWay manual alert, and TradingView alerts to broker.
The route is:
Manual TradingView condition → TradingView webhook URL → AlgoWay webhook → broker, exchange or trading platform
This guide focuses on manual alerts created from TradingView chart conditions. It also explains how to use AlgoWay's test webhook tool when you want to test the same JSON without waiting for a TradingView alert to trigger.
Last updated: 2026-05-12 • Author: AlgoWay
To create a manual TradingView webhook alert for AlgoWay:
Basic manual BUY alert:
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_contracts": "1",
"order_action": "buy"
}
TradingView replaces {{ticker}} when the alert fires. The size and action are fixed because this is a manual alert, not a strategy-generated order.
Manual alerts and strategy alerts are different. Use the correct message style for the alert type.
| Alert type | Typical trigger | Typical JSON | Best use case |
|---|---|---|---|
| Manual alert | Price crossing, drawing, condition, indicator value | Fixed action and fixed size | Simple manual automation and route testing |
| Strategy alert | Pine Script strategy order event | {{strategy.order.contracts}}, {{strategy.market_position}} |
Fully automated strategy execution |
| Indicator alert | Indicator alertcondition or custom alert | Fixed or indicator-generated JSON | Indicator-based trading signals |
For full strategy automation, use the central guide: How to create a TradingView webhook alert.
Manual TradingView webhook alerts are useful when you want control without writing or running a full strategy.
Use manual alerts when:
Manual alerts are not ideal for advanced position logic unless you create clear entry, exit and risk alerts separately.
Prepare the following:
Open the AlgoWay dashboard and copy the webhook URL for the route you want to test or automate.
Webhook URL format:
https://algoway.co/your-webhook-uuid
The old version of this guide showed an example webhook URL. That example is not a live value for your account. Always use the URL generated by your own AlgoWay dashboard.
Open TradingView and create the alert from the chart condition you want to use.
For a price-crossing alert, the message can be fixed because the condition itself decides when the command is sent.
Each TradingView alert should contain one valid JSON message. Do not paste several JSON blocks into one alert.
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_contracts": "0.01",
"order_action": "buy"
}
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_contracts": "0.01",
"order_action": "sell"
}
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_action": "flat"
}
{
"platform_name": "coinbase",
"ticker": "BTC-USD",
"order_contracts": "0.001",
"order_action": "buy"
}
{
"platform_name": "projectx",
"ticker": "MNQ",
"order_contracts": 1,
"order_action": "buy"
}
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_contracts": "0.01",
"order_action": "buy",
"price": "{{close}}"
}
Use {{close}} when you want AlgoWay logs to include the TradingView close price at alert time.
The most common manual values are:
| Value | Meaning | Typical manual use |
|---|---|---|
buy |
Open or process a buy-side command. | Price crosses above a resistance level. |
sell |
Open or process a sell-side command. | Price crosses below a support level. |
long |
Directional long value where supported. | Indicator produces long condition. |
short |
Directional short value where supported. | Indicator produces short condition. |
flat |
Close or flatten logic where supported. | Exit condition or manual close alert. |
The exact effect depends on the destination platform and AlgoWay trade mode. Read: How AlgoWay handles opposite trading signals.
If the route supports SL/TP fields, you can add them to the fixed JSON message.
{
"platform_name": "metatrader5",
"ticker": "{{ticker}}",
"order_contracts": "0.01",
"order_action": "buy",
"stop_loss": "100",
"take_profit": "200"
}
Before live use, confirm whether your route interprets stop_loss and take_profit as points, pips, percent or another configured distance model.
Test the route before using live size.
If you do not want to wait for TradingView, use AlgoWay's test webhook tool.
AlgoWay also lets you test payload delivery directly from the dashboard:
This is useful for testing syntax, credentials, EA connection and broker/exchange acceptance before using TradingView.
AlgoWay logs help identify where a manual alert failed.
| Observation | Likely meaning |
|---|---|
| No new log entry | TradingView did not send the webhook, the URL is wrong, or the alert did not trigger. |
| Payload received but JSON error | The message is not valid JSON. |
| Payload received but platform rejected | Destination credentials, symbol, size, session, margin or platform rules rejected the order. |
| Payload received and order accepted | The route works. Continue testing exits and risk behavior. |
The JSON message alone is not enough. In TradingView, open Notifications and enable Webhook URL.
Do not use documentation example URLs. Use the real AlgoWay webhook URL from your dashboard.
Use double quotes, correct commas and one JSON object. Broken JSON can trigger Error 415. Read: How to fix AlgoWay webhook Error 415.
If the webhook route is ProjectX but the JSON says metatrader5, the signal can be routed incorrectly or rejected.
TradingView {{ticker}} may not match the broker or exchange symbol. Check symbol mapping.
The size must match platform rules. MT5 uses lots, futures usually use whole contracts, and crypto exchanges may require minimum quantity or step size.
Check TradingView frequency. For many manual alerts, use a controlled one-time trigger or clear alert management.
Check whether flat is supported for the route, whether the symbol matches, and whether the position belongs to the same account and route logic.
Before live manual automation, confirm:
platform_name matches the route;Manual TradingView webhook alerts are the simplest way to send fixed trading commands to AlgoWay. Create a price or condition alert, paste one valid JSON message, enable the AlgoWay webhook URL, trigger the alert, and verify the result in AlgoWay Webhook Logs.
Use manual alerts for simple price-level automation, route testing and fixed buy/sell/flat commands. Use strategy alerts when the order size and direction should come from Pine Script strategy logic.