Automations - Deleted Tasks or Branching
Automations continue to run for tasks that have been deleted. Branching automations would be very helpful in preventing these issues, as it could aggravate the recipients and cause confusion.
For example " I thought I rescheduled my appointment, but I'm still getting texts for an appointment at 8AM?! What is going on?!"
Branching would allow us to say: When A happens, if B is true, then do C. BUT If B is false, then do D instead (or do nothing).
Leighton Ross
shared this idea
-
IF you wanted to go so far as to include branching, you could lump the Condition and Action sections together and include the ability to add more Condition/Action sets to the same trigger.
-
The solution is already halfway there, we just need to configure the second half.
As of right now we can already Trigger based on a deleted "item", and lots of valuable filters.
The problem and proposed solution lie in the action category.
It would add tremendous value if we could say +Add Action > Automation > Automation Dialog Box
In the Dialog Box, one should be able to reference the Name of the Automation and select an action... in this case the most immediate need would be to STOP the triggering of automations if a task is deleted.
However, once this is available there may be many more impactful and valuable applications for the ability to reference other automations such as...
-Update Field Data if a task/event/etc is modified
-Add the ability to reference automation to the conditions section so that you could say "if Automation stops, then notify ____ or create a task, etc etc" -
A workaround for doing this might be creating the ability to reference existing automations and create STOP actions.