Introducing Automation "Switches"

We’re always listening to the Community and continuously make improvements based on your feedback. We saw how you were using tags to toggle features on and off, so we decided to create a switch to make that process more user-friendly.

Imagine turning off an entire automation or certain branches of your automation.

That’s exactly what automation switches enable you to do.

There is a brand new decision recipe for “Switch is on/off” that allows you to toggle a switch on or off inside an automation.

Switches are incredibly flexible and give you even more control of your bots. 

If a switch is on, the automation continues down the “Yes” path. If the switch is off, the automation proceeds down the “No” path. If there are no actions after the switch, the automation simply ends.

The possibilities are limitless, and we already see some very cool use cases in the Community.

For example, you could add a switch to the top of a scanner that controls whether the automation is allowed to scan or not. This is a great way to essentially “turn off” a scanner if you don't want to open new positions, but you still want the bot to manage existing positions with monitor automations.

In the example above, if the switch is “Off” the automation will not run because the switch begins the automation.

You have total control of the switch right inside your automation settings.

What if you only want to check a certain part of an automation? Glad you asked.

This “Check RSI Levels” switch determines if the automation will check RSI levels.

You can turn the switch “On” when you want to check RSI levels, or turn the switch “Off” if you don’t want to check RSI levels. It’s that simple.

Plus, you can send this to a bot-level input and have multiple switches that control different parts of an automation.

The combination of bot tags, position tags, and now switches takes bot building to a completely new level and gives you the ability to make precise, specific decisions.