The Automation Editor is where you tell the bot what decisions to make, what criteria to look for, and what actions to take. The Automation Editor follows a decision tree framework where criteria are evaluated in a step-by-step, if-then format.
Adding an automation (:48)
To add a new automation, select the "+" symbol to access your automations. You can choose an automation from your library or create a new automation.
You can name the new automation, save it to your library, and create folders to keep your automations organized.
Adding an action (1:23)
To add actions to the automation's decision tree, select the "+" symbol inside the editor. A list of available actions is displayed.
Decision actions are split into conditional yes/no paths and can end with an open position action, close position action, or a notification.
Actions include:
- Decision - The decision action enables a bot to make yes / no decisions dynamically inside an automation.
- Open Position - The open position action tells the bot to send an order to your broker. The open position action gives you complete control of when and why a position is opened.
- Close Position - The close position action enables the bot to close positions and gives you complete control of when and why a position is closed.
- Repeater - The repeater action repeats through positions and applies all subsequent actions to the specified position types in an automation.
- Notification - Send yourself a notification inside the platform.
Decision recipes (1:54)
Decision recipes are used to build out an automaton. There are dozens of recipes to choose from, and each recipe is unique. Decision recipes use specific criteria to reference market and position data and use natural language for simplicity.
For example, this decision recipe checks if SPY is above the 200-day simple moving average before proceeding through the automation.
Select "Save," and the decision is added to the automation editor.
Additional actions can be added to the "Yes" and "No" paths to complete the automation. Scanners typically end with an open position action. Monitor automations usually end with a close position action or an action that triggers an adjustment.
You do not need to put an action at the end of the decision tree if the necessary criteria is not met to open a position. For example, if the SPY price is below the 200-day SMA, the “No” branch of the automation will end, and the automation will stop until its next interval.
Editing an automation (3:46)
Editing an existing automation inside a bot is easy. You have the flexibility to change the automation and workflow of decisions in your bots at any time.
To edit the automation, simply hover the mouse over the automation and select the icon. All edits are automatically saved every time you make changes.
Inside the automation editor, you may select any decision action and change the variables you wish to edit. When you are finished, click save, and the updated decision will now be reflected in your bot’s automation editor.
If you use the same automation for multiple bots, editing the automation in one bot updates all bots. Because the automation is automatically updated across your library of bots, you do not need to remember everywhere you used a particular automation—your automation edit is already saved anywhere the automation is used.
Testing an automation (4:31)
You can also test an automation once it is complete. Select "Test" from the top of the automation editor.
The test moves through the decision recipes and scans current market conditions. This is a great way to check that everything is working how you intend before using the automation in a live setting.
When the automation is complete, select the "X" in the top right corner, and the automation is added to your bot. The timestamp in the bottom left corner tells you when the automation was last saved.
