Currently, in SmartSuite, I need to create separate automations for each service to create tasks. It would be more efficient to have conditional actions within automations, allowing for branching paths. This would simplify the process of creating tasks based on multiple linked records, reducing the need for numerous individual automations and making the system more flexible and easier to manage.

I need to perform different actions based on whether a condition is met or not, but the current system doesn't support this. Implementing conditional branching in automations would allow me to execute different paths based on the outcome of a condition, which is crucial for my workflow.

I am struggling with the lack of conditional logic in automations. I need an automation to check if a person's name exists in another table and update a status field accordingly. Currently, the automation shows an error in the history if a record is not found, which is confusing. I would like the ability to handle the result conditionally without generating an error, or at least have a more specific message like 'record not found.'

I am trying to use automation to update records based on email matches, but SmartSuite currently lacks conditional logic in automation actions. This feature would allow me to set conditions directly within SmartSuite, eliminating the need for third-party tools like Make. It would streamline my workflow by enabling more complex automation scenarios directly within the platform.

I am building a custom CRM where I need to link records between leads and contacts. I want the system to automatically check if a contact exists when a new lead is added, and create a new contact if none is found. Currently, I can achieve this using Zapier, but it would be great to have this functionality natively in SmartSuite. This feature would streamline the process and reduce dependency on external tools.

Could we please add the ability for an "IF Error, Then..." path of an automation? Currently, if a node in the automation fails, in some automations, this turns off the automation completely. Rather, I'd like for the automation to take an error path that updates a status of the record it's working with to "Needs Review" (or some status choice), notifies our team as it already does, but NOT turn off the automation.