Decision Trees in Automations

Automations right now are single focused. Having multi layered/outcome automations. We use this in other systems to route the right actions based on specific criteria. I believe that a decision tree within automations would be a great resource to make this happen.

Absolutely, that makes a lot of sense. Single-focused automations can be limiting, especially when you’re trying to handle more complex workflows. Introducing multi-layered outcomes through a decision tree sounds like a smart move—it gives the system the ability to adapt based on specific conditions, just like we see in more advanced routing setups. Even something as simple as a flip a coin logic could be used creatively here, especially when multiple valid outcomes exist and you want to add a bit of randomness or distribute actions evenly. A well-structured decision tree could really take your automation game to the next level.

Hello! Shannon here with the monday team. :waving_hand: Following up on this feature request! Yes, while board automations are single-focused, a new feature was launched this past year to address this gap for users: monday workflows. You can read more about it here: What is monday workflows? > And how does it work?

This feature is only available to users on the Enterprise Plan tier, but it allows users to build out a tree of automated actions and build in conditions or delays! Let me know if you both have any additional questions. :slightly_smiling_face:

Workflows only partially solve this problem. Readers may want to upvote the related feature request: