Leighton Ross
My feedback
111 results found
-
13 votes
-
14 votes
-
3 votes
-
23 votes
-
2 votes
-
18 votes
-
2 votes
-
59 votes
-
32 votes
-
5 votes
An error occurred while saving the comment -
5 votes
-
5 votes
-
4 votes
-
5 votes
An error occurred while saving the comment 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.
An error occurred while saving the comment 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"An error occurred while saving the comment A workaround for doing this might be creating the ability to reference existing automations and create STOP actions.
-
5 votes
-
11 votes
-
7 votes
-
6 votes
-
2 votes
-
7 votes
YES!!!!!!!