Strategy Automation

How to Automate an AlgoPro Strategy

Overview

Many AlgoPro strategies include automation command fields. These fields are used to send custom messages through TradingView alerts.

Automation is commonly used to connect a TradingView strategy to:

• A broker bridge

• A trade copier

• A webhook server

• An execution bot

• A prop-firm compatible platform

• A third-party automation service

The strategy itself does not place live trades directly unless it is connected to an automation system. TradingView sends an alert, and the automation platform reads that alert and executes the order.

---

Important Automation Warning

Only automate a strategy after it has been fully tested.

Before going live, users should confirm:

• The strategy entries make sense.

• Take profits and stop losses are working.

• Alerts fire correctly.

• Alert messages are correct.

• Position size is correct.

• The broker/execution platform receives the commands correctly.

• The strategy does not overtrade.

• The account risk is acceptable.

A wrong alert command can open, close, or size trades incorrectly.

---

How AlgoPro Strategy Alerts Work

AlgoPro strategies usually have command fields such as:

• Open Long Command

• Open Short Command

• Long TP1 Command

• Long TP2 Command

• Long TP3 Command

• Long TP4 Command

• Long TP5 Command

• Short TP1 Command

• Short TP2 Command

• Short TP3 Command

• Short TP4 Command

• Short TP5 Command

• Long 100% Close Command

• Short 100% Close Command

The user enters the automation message required by their broker bridge or automation platform into these fields.

When the strategy places an order, TradingView sends the matching command.

---

The Most Important Alert Message

When creating a TradingView strategy alert, the message box should usually be:

{{strategy.order.alert_message}}

This placeholder tells TradingView:

Send the alert message attached to the specific strategy order that just triggered.

Without this placeholder, the strategy may not send the correct open, close, or take-profit command.

---

Basic Automation Workflow

Step 1: Choose the strategy

Add the AlgoPro strategy to the TradingView chart.

Examples:

• AlgoPro Quantum

• AlgoPro Nova

• AlgoPro Nexus

• AlgoPro Gamma

• AlgoPro QuantFlow

• AlgoPro AlphaX

• AlgoPro RevQ

• AlgoPro EvoQ

• AlgoPro EvoX

• AlgoPro V1.4 Bot

• Scalper Bot V3

Open the strategy settings.

---

Step 2: Configure entries and exits first

Before entering automation commands, make sure the strategy itself behaves correctly.

Check:

• Long trades

• Short trades

• Take profits

• Stop losses

• Break-even movement

• Trailing stop behavior

• Session filters

• Daily limits

• Cooldowns

Do not automate until the backtest and chart behavior look correct.

---

Step 3: Find the automation command fields

Inside the strategy settings, look for the automation or command section.

The exact section name may vary, but it usually includes fields like:

Open Long Command
Open Short Command
Long TP1 Command
Short TP1 Command
Long 100% Close Command
Short 100% Close Command

These fields are where the user pastes their automation commands.

---

Step 4: Paste the correct commands

The exact command format depends on the automation provider.

A command may be plain text, JSON, or another format.

Examples:

{
  "action": "buy",
  "symbol": "{{ticker}}",
  "quantity": 1
}

{
  "action": "sell",
  "symbol": "{{ticker}}",
  "quantity": 1
}

OPEN_LONG

CLOSE_SHORT

The user should follow the command format required by their automation platform.

---

Step 5: Create a TradingView alert

After the commands are entered:

1. Click Alerts in TradingView.

2. Click Create Alert.

3. Choose the AlgoPro strategy as the condition.

4. Select the strategy order alert option.

5. In the message box, enter:

{{strategy.order.alert_message}}

1. Add the webhook URL if the automation platform requires one.

2. Choose alert frequency according to the platform instructions.

3. Create the alert.

---

Step 6: Add the Webhook URL

Most automation systems require a webhook URL.

This is the destination TradingView sends the alert to.

The webhook URL usually comes from:

• Broker bridge

• Trade copier

• Automation bot

• Algo execution platform

• Your own server

Paste that URL into TradingView’s Webhook URL field.

Only use webhook URLs from services you trust.

---

Recommended Alert Frequency

For strategy alerts, users usually want the alert to trigger when the strategy order fills.

Depending on TradingView’s available options, use the setting that corresponds to strategy order execution.

Avoid using random indicator alert conditions if the strategy is designed to use {{strategy.order.alert_message}}.

---

Example Automation Setup

Example command fields

Inside the strategy settings:

Open Long Command:
{"action":"open_long","symbol":"{{ticker}}","qty":1}

Open Short Command:
{"action":"open_short","symbol":"{{ticker}}","qty":1}

Long 100% Close Command:
{"action":"close_long","symbol":"{{ticker}}"}

Short 100% Close Command:
{"action":"close_short","symbol":"{{ticker}}"}

If the strategy uses multiple take profits:

Long TP1 Command:
{"action":"close_long_partial","symbol":"{{ticker}}","percent":25}

Long TP2 Command:
{"action":"close_long_partial","symbol":"{{ticker}}","percent":25}

Long TP3 Command:
{"action":"close_long_partial","symbol":"{{ticker}}","percent":25}

Long TP4 Command:
{"action":"close_long_partial","symbol":"{{ticker}}","percent":25}

Then the TradingView alert message should still be:

{{strategy.order.alert_message}}

---

Automation With Multiple Take Profits

Strategies with TP1–TP5 commands can send different messages for each target.

For example:

• TP1 may close 25%.

• TP2 may close another 25%.

• TP3 may close another 25%.

• TP4 may close the rest.

The automation platform must support partial closes for this to work correctly.

If the automation platform does not support partial closes, the user may need to:

• Use only one take profit

• Use 100% close commands

• Disable partial TP commands

• Configure the bridge to translate partial closes correctly

---

Automation With Stop Loss

Many strategies use the 100% close command for full exits.

A full close may happen because of:

• Stop loss

• Opposite signal

• Trailing stop

• Break-even stop

• Session close

• Daily lock

• Early close logic

That is why the Long 100% Close Command and Short 100% Close Command are important.

They are not only for manual closes. They may be used anytime the strategy needs to fully exit the position.

---

Automation With Break Even and Trailing Stops

Break-even and trailing stops can cause full exits after the trade is already open.

Users should make sure the close command is correct before enabling these features.

For example, if a trailing stop closes a long trade, the strategy needs to send the correct long close command.

If the close command is wrong, the automation platform may fail to close the trade or may close the wrong side.

---

Automation With Session Close

Some strategies include:

• Close at end of session

• Close on daily loss lock

• Close on daily profit lock

• Close on avoid window

• Close early after X bars

These can also trigger full close commands.

If users enable these features, they should test that the automation platform receives and handles the close command correctly.

---

Testing Automation Safely

Step 1: Use paper trading or demo mode

Never test automation for the first time on a live account.

Use:

• TradingView paper trading

• Broker demo account

• Automation platform paper mode

• Minimum possible size

Step 2: Test each command

Trigger and confirm:

• Open Long

• Close Long

• Open Short

• Close Short

• TP1

• TP2

• Stop loss

• Opposite signal close

• Session close

Step 3: Check the logs

Most automation platforms provide logs.

Confirm:

• The alert was received.

• The command was parsed correctly.

• The symbol was correct.

• The side was correct.

• The size was correct.

• The order type was correct.

Step 4: Start small

After paper testing, use the smallest possible live size first.

Do not immediately automate full size.

---

Common Automation Mistakes

Forgetting {{strategy.order.alert_message}}

This is the most common mistake.

If the user types a fixed message instead, TradingView may send the same message for every order.

That means TP, SL, open long, open short, and close commands may not work correctly.

Putting commands only in the TradingView alert box

The alert box should usually contain:

{{strategy.order.alert_message}}

The actual commands go inside the strategy settings.

Wrong webhook URL

If the webhook URL is wrong, the automation platform will not receive the alert.

Wrong symbol format

Some platforms require specific symbols.

For example, TradingView may use one symbol format, while the broker uses another.

Users should confirm symbol mapping with their automation provider.

Wrong order quantity

If quantity is inside the command, make sure it matches the intended risk.

If quantity is controlled by the platform, make sure the platform settings are correct.

Partial closes not supported

Some platforms do not support partial closes the same way TradingView does.

Test TP1–TP5 carefully.

Strategy settings changed but alert not recreated

In some cases, TradingView alerts may need to be recreated after major strategy setting changes.

If alerts act wrong after changing settings, recreate the alert.

Recalculate settings

Some strategies and trailing systems may behave differently depending on TradingView recalculation settings.

If a strategy uses intrabar logic, trailing exits, or recalculation after order fill, test alerts carefully before live use.

---

Recommended Automation Checklist

Before going live, confirm:

[ ] Strategy entries look correct on chart
[ ] TP/SL levels look correct
[ ] Position size is correct
[ ] Automation command fields are filled
[ ] TradingView alert uses {{strategy.order.alert_message}}
[ ] Webhook URL is correct
[ ] Open Long tested
[ ] Close Long tested
[ ] Open Short tested
[ ] Close Short tested
[ ] TP commands tested
[ ] Stop loss close tested
[ ] Session close tested if enabled
[ ] Paper/demo test completed
[ ] Live test done with smallest size first

---

Best Practices for Automation

Use automation only after the strategy has been tested.

Keep the first setup simple:

• One open long command

• One open short command

• One full close long command

• One full close short command

• One take profit if needed

After that works, add more advanced features:

• Multiple take profits

• Break-even

• Trailing stop

• Session close

• Daily locks

• DCA or scaling

The key idea:

Automate the simple version first. Once the basic open and close commands work perfectly, then add advanced trade management.