[Automations] Possibility for an automation to be triggered by a change of state generated by another automation (not just manually)

Hey Giovanni De Giovanni, could you please clarify if by "change of state" you mean status change, or is it something else? Thanks! 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Hi Lisa, yes, I do absolutely mean "status change" (I apologize if I was not clear in describing it).

Thanks a lot for clarifying Giovanni De Giovanni! I've now discussed your feedback with the team and for now, it's not possible to have an automation rule trigger another rule. Our team is aware of this and they would like to address this in the future.

Thank you for your feedback and for posting your idea 🙌

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Hi Lisa, thanks a lot for your message. I truly hope that this implementation can be seriously considered and maintained in your development pipeline, as it would objectively mark a significant change from the past, providing the opportunity to customize the workflows of Wrike's customers (I'm not referring to workflows in the technical sense used by Wrike - new-in-progress-etc. - but in a broader sense) and reducing the reliance on external automation tools like Workato and Zapier.

Lisa - What is the progress of adding this into Wrike? I would also love to have this be a possibility as well!

Rohan V Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Rohan V Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Hi Rohan,

Since I was the author of the first message, and given that more than a year has passed since I wrote it, I’ve had the opportunity over the past year to analyze the situation more deeply and encounter further limitations that, unfortunately, Wrike’s internal automations still have.

In light of the experience I have gained over this year, I would like to broaden the context of the original request a bit.
What I (and I believe many other Wrike users as well) would like to see is that Wrike’s internal automations are actually triggered by the event indicated in the "Trigger" section when creating a new automation, and that the current limitations are removed, such as:

• The automation does not trigger if the event that should trigger it (theoretical trigger) was performed by another internal automation;
• The automation does not trigger if the task that should trigger it was created via Blueprint;
• The automation does not trigger if the task that should trigger it was created via Workato.

Unfortunately, all these scenarios paralyze the "automate-ability" of operations, undermining trust in the tool because, when setting up a workflow, you’re forced to ask yourself a thousand preliminary questions to avoid the possibility that any of the real-life cases you will encounter might fall into one of the limitations I described.

It’s a real shame because, apart from these limitations, the internal automations menu would be quite complete and certainly suitable for managing a large number of automations without having to resort to using Workato, which could then be reserved for handling more complex automations.

I am available to provide further information if necessary.

Thank you, and good work, Giovanni

Rohan V Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Rohan V Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online