Add "run another automation" as a choice for when step fails
Kaitlin Pierce
One of my biggest holdups with using the native automation in SmartSuite is the lack of branching logic. I wonder if a workaround feature might be adding an option to specify a linked secondary automation rather than just "continue" or "fail" if conditions aren't met. Example use case: when adding data to a table that will then roll up into a junction table, I want my automation to first try to "Find record" to link the new data record to based on set parameters. If it can't find an existing rollup in the junction table, I don't want it to continue or fail, I want it to instead run a different automation that will make the needed rollup record. That secondary automation might have a trigger like "if automation fails"... This would allow stringing of actions rather than directly creating branching logic since the UI doesn't really seem like it would support it well.
Jon Darbyshire
Great to hear your perspective, Kaitlin Pierce! I have a few more questions for you:
- Can you provide more details about the specific conditions that should trigger the secondary automation?
- What are the expected outcomes when the secondary automation is triggered?
- Could you elaborate on the 'parameters' you mentioned for linking the new data record?
Kaitlin Pierce
Jon Darbyshire sure! Here's my thought: The simplest way I can envision something like this would be as a Trigger type "When automation fails." So let's say I have a contact form that collects new contacts for me and adds them as records to my solution's "contacts" table. Then I have an automation that triggers when a new record is created in "contacts" that looks up the associated organization and location that this person should be linked to in order to update that record by appending the new contact. If that search for a location fails because none of the search conditions are met and I set it to "Fail" if none are found, this new automation would "catch" the signal by triggering in response to that other automation's failure. You would be able to specify which automation failing would be the trigger rather than choosing which table in the initial setup. Then, it could either email alert someone with all the details for the new contact to ensure there truly isn't an existing location and set it up/follow up with that contact to create a new one. Pictures attached.